Answer guardrail prompt
guardrail_responseRespond to a guardrail trigger when the browser agent needs human input (credentials, clarification, approval). The response is handed to the live agent, which continues acting on it.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"sessionId": "<sessionId>"
},
"name": "guardrail_response"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| askId | No | The question's askId (from get_task_status), when known: refused if that question is no longer waiting. | |
| files | No | Optional file IDs to attach: ids returned by POST /files/upload, or any file already in one of the user's environment catalogs (GET /environments/:id/files). Max 5 files. | |
| newState | No | How to continue: 'resume' (default) provides the requested input and continues the task; 'deny' declines the request (response text optional). | |
| response | No | Your response/instructions to the agent. Required when newState is 'resume'. | |
| decisions | No | For an approval question (one listing numbered drafts): a decision per draft number. Without it, response must be in the fixed format 1 send · 2 edit: "new text" · 3 skip. | |
| sessionId | Yes | Session ID |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| taskId | No | ||
| message | No | What happened and what to do next (poll get_task_status) | |
| success | Yes | ||
| sessionId | No |