Unregister an agent from the communication framework. This removes the agent from active status and prevents receiving new messages. Only unregister your own agent ID.
AI agents use unregister-agent to create or update resources in MCP Agentic Framework — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Agentic Framework environment.
This tool modifies system state by deactivating an agent's registration, preventing it from receiving messages. While labeled 'unregister,' it is reversible (the agent could be re-registered), distinguishing it from Destructive operations. The instruction 'Only unregister your own agent ID' provides access control but doesn't change the classification.
From the tool's definition Tool description states it 'removes the agent from active status and prevents receiving new messages' — an irreversible state change to agent registration records.
Documented attack patterns abuse exactly the kind of access unregister-agent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Agentic Framework, and nothing reaches the server without passing your rules. This is the rule we recommend for unregister-agent:
{
"version": "1",
"default": "deny",
"tools": {
"unregister-agent": {
"limits": [
{
"counter": "unregister-agent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unregister-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.
Free to start. No card required.
Unregister an agent from the communication framework. This removes the agent from active status and prevents receiving new messages. Only unregister your own agent ID. It is categorised as a Write tool in the MCP Agentic Framework MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Agentic Framework MCP server in PolicyLayer and add a rule for unregister-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 MCP Agentic Framework. Nothing to install.
unregister-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 unregister-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 unregister-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.
unregister-agent is provided by the MCP Agentic Framework MCP server (piotr1215/mcp-agentic-framework). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Agentic Framework, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 MCP Agentic Framework tools catalogued and risk-classified — across an index of 43,000+ MCP servers.