Medium Risk

a2a_send_task

Send a task to an A2A agent

How to control a2a_send_task ↓

AI agents use a2a_send_task to create or update resources in A2A Client MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your A2A Client MCP Server environment.

Medium Risk

An AI agent can call a2a_send_task faster than any human can review — one bad instruction and it creates or modifies resources in A2A Client MCP Server by the hundred, each call as confident as the last.

Documented attack patterns abuse exactly the kind of access a2a_send_task gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and A2A Client MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for a2a_send_task:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "a2a_send_task": {
      "limits": [
        {
          "counter": "a2a_send_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

a2a_send_task 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.

  1. Create a free account and register A2A Client MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the a2a_send_task tool do? +

Send a task to an A2A agent. It is categorised as a Write tool in the A2A Client MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on a2a_send_task? +

Register the A2A Client MCP Server MCP server in PolicyLayer and add a rule for a2a_send_task: 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 A2A Client MCP Server. Nothing to install.

What risk level is a2a_send_task? +

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

Can I rate-limit a2a_send_task? +

Yes. Add a rate_limit block to the a2a_send_task 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.

How do I block a2a_send_task completely? +

Set action: deny in the PolicyLayer policy for a2a_send_task. 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 a2a_send_task? +

a2a_send_task is provided by the A2A Client MCP Server MCP server (tesla0225/mcp-a2a). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every A2A Client MCP Server tool call.

Deterministic rules across all 5 A2A Client MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

5 A2A Client MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.