create_agent
A write tool on the A2a Cloud MCP server.
This record as markdown: /tools/a2a-cloud/create-agent.md
What create_agent does on A2a Cloud
AI agents use create_agent to create or update resources in A2a Cloud, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your A2a Cloud environment.
Why create_agent is rated Medium
Creating agents in a long-term memory system is a reversible modification operation (Write category). Severity is medium because misuse could spawn unauthorized agents, pollute the memory store, or interfere with legitimate CLI workflows, but the impact is limited to agent metadata rather than financial or destructive system changes.
From the tool's definition Tool name 'create_agent' indicates creating new agent records in a long-term memory system. The server description mentions 'cross-CLI, cross-project, cross-session' persistence, and sibling tools like 'delete_agent', 'list_agents', and 'wiki_write_concept'…
Attacks that exploit this kind of access
The rule that runs create_agent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A2a Cloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_agent, this is the rule to start with:
create_agent 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 A2a Cloud, apply this rule, and every create_agent call is checked against it from then on.
Questions about create_agent
create_agent is a write tool on the A2a Cloud MCP server. It is categorised as a Write tool in the A2a Cloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the A2a Cloud MCP server in PolicyLayer and add a rule for create_agent: 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 Cloud. Nothing to install.
create_agent 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 create_agent 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 create_agent. 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.
create_agent is provided by the A2a Cloud MCP server (robGetsTheJobDone/a2a-cloud). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A2a Cloud, and thousands of servers like it.
This server
Across the catalogue