Using zirc_getQuarantined, you can also query all quarantined transactions and filter them by addresses.
AI agents call zirc_getQuarantined to retrieve information from Ethereum RPC MPC Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters existing blockchain data (quarantined transactions) without side effects. It is a read-only operation analogous to a database SELECT query. While it accesses blockchain state, the read-only nature and lack of any ability to execute transactions, modify state, or trigger external operations places it firmly in the Read category.
From the tool's definition Tool description states 'query all quarantined transactions and filter them by addresses' — pure data retrieval with no modification, creation, deletion, or financial transaction capability.
Documented attack patterns abuse exactly the kind of access zirc_getQuarantined gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ethereum RPC MPC Server, and nothing reaches the server without passing your rules. This is the rule we recommend for zirc_getQuarantined:
{
"version": "1",
"default": "deny",
"tools": {
"zirc_getQuarantined": {}
}
}zirc_getQuarantined is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Using zirc_getQuarantined, you can also query all quarantined transactions and filter them by addresses. It is categorised as a Read tool in the Ethereum RPC MPC Server MCP Server, which means it retrieves data without modifying state.
Register the Ethereum RPC MPC Server MCP server in PolicyLayer and add a rule for zirc_getQuarantined: 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 Ethereum RPC MPC Server. Nothing to install.
zirc_getQuarantined 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_getQuarantined 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_getQuarantined. 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_getQuarantined is provided by the Ethereum RPC MPC Server MCP server (kemperino/ethereum-rpc-mpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ethereum RPC MPC Server, 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.
3 Ethereum RPC MPC Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.