zirc_isQuarantined
AI agents call zirc_isQuarantined to retrieve information from Chain Debugger MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description reducing confidence slightly, the naming convention strongly indicates this tool retrieves status information rather than modifying, executing, or deleting data. It fits the 'Read' category as a monitoring/query operation. No financial impact, execution risk, or destructive capabilities are implied by the name.
From the tool's definition Tool name 'zirc_isQuarantined' suggests a status check or query operation. Given the context of a blockchain debugging server, this appears to be checking whether an address or contract is in a quarantined/flagged state.
Attacks that exploit this kind of access
zirc_isQuarantined. It is categorised as a Read tool in the Chain Debugger MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chain Debugger MCP Server MCP server in PolicyLayer and add a rule for zirc_isQuarantined: 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 Chain Debugger MCP Server. Nothing to install.
zirc_isQuarantined is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the zirc_isQuarantined 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 zirc_isQuarantined. 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.
zirc_isQuarantined is provided by the Chain Debugger MCP Server MCP server (optimusopus/chain-debugger-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →