unblock_agent
Unblock a previously blocked agent
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/unblock-agent.md
What unblock_agent does on MIDAS Protocol
AI agents use unblock_agent to create or update resources in MIDAS Protocol, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MIDAS Protocol environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
agentId | string | Yes |
Parameters from the server's own tool schema.
Why unblock_agent is rated Medium
This tool reverses a prior block action, modifying the access/trust state of an agent relationship. It is a reversible write operation (the agent can be re-blocked), but misuse could expose the user to interactions with malicious or unwanted agents, giving it medium severity.
From the tool's definition Unblock a previously blocked agent
Attacks that exploit this kind of access
The rule that runs unblock_agent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MIDAS Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unblock_agent, this is the rule to start with:
unblock_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 MIDAS Protocol, apply this rule, and every unblock_agent call is checked against it from then on.
Questions about unblock_agent
Unblock a previously blocked agent. It is categorised as a Write tool in the MIDAS Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
unblock_agent accepts 1 parameter: agentId. Required: agentId. The full parameter table on this page comes from the server's own tool schema.
Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for unblock_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 MIDAS Protocol. Nothing to install.
unblock_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 unblock_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 unblock_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.
unblock_agent is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MIDAS Protocol, and thousands of servers like it.
This server
Across the catalogue