agents_reject_draft
Reject a pending agent draft without sending. The draft will be marked as rejected and won't be sent. Use this when the generated response isn't appropriate. Use this when user says: - 'Reject this draft' - 'Don't send this' - 'Cancel this reply' - 'Delete this draft' - 'This response is wrong'
This record as markdown: /tools/io-github-saloprj-dialogbrain/agents-reject-draft.md
What agents_reject_draft does on Dialogbrain
AI agents use agents_reject_draft to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | Optional reason for rejection (for logging/feedback) |
draft_id | integer | Yes | ID of the draft to reject |
Parameters from the server's own tool schema.
Why agents_reject_draft is rated Medium
This tool modifies data (changes draft status to rejected) reversibly—the draft remains in the system and can be recovered or recreated. It does not permanently delete the draft, execute external code, or move money.
From the tool's definition Tool modifies the state of a draft message by marking it as rejected without sending it. Description states 'The draft will be marked as rejected and won't be sent,' indicating a state change operation that is reversible and does not delete data.
Attacks that exploit this kind of access
The rule that runs agents_reject_draft safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agents_reject_draft, this is the rule to start with:
agents_reject_draft stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every agents_reject_draft call is checked against it from then on.
Questions about agents_reject_draft
Reject a pending agent draft without sending. The draft will be marked as rejected and won't be sent. Use this when the generated response isn't appropriate. Use this when user says: - 'Reject this draft' - 'Don't send this' - 'Cancel this reply' - 'Delete this draft' - 'This response is wrong'. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
agents_reject_draft accepts 2 parameters: reason, draft_id. Required: draft_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for agents_reject_draft: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Dialogbrain. Nothing to install.
agents_reject_draft is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the agents_reject_draft rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for agents_reject_draft. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
agents_reject_draft is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue