Medium Risk

send_task_message

Send a message to the human worker on one of your tasks. Use this to answer a clarifying question, add context, or follow up. Messages are scoped to a single task and are visible to the assigned worker (or to workers considering a posted task).

Accepts raw HTML/template content (body); Single-target operation

Part of the Reversecentaur MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

reversecentaur-mcp Write Risk 2/5

AI agents use send_task_message to create or modify resources in Reversecentaur. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call send_task_message repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Reversecentaur.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-brandonbgreen-reversecentaur-mcp.yaml
tools:
  send_task_message:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Reversecentaur policy for all 6 tools.

Tool Name send_task_message
Category Write
Risk Level Medium

Agents calling write-class tools like send_task_message have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the send_task_message tool do? +

Send a message to the human worker on one of your tasks. Use this to answer a clarifying question, add context, or follow up. Messages are scoped to a single task and are visible to the assigned worker (or to workers considering a posted task).. It is categorised as a Write tool in the Reversecentaur MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_task_message? +

Add a rule in your Intercept YAML policy under the tools section for send_task_message. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Reversecentaur MCP server.

What risk level is send_task_message? +

send_task_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit send_task_message? +

Yes. Add a rate_limit block to the send_task_message rule in your Intercept 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.

How do I block send_task_message completely? +

Set action: deny in the Intercept policy for send_task_message. 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.

What MCP server provides send_task_message? +

send_task_message is provided by the Reversecentaur MCP server (reversecentaur-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Reversecentaur

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.