AI agents call anvil_status to retrieve information from Foundry MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves the current status of an Anvil instance (a local blockchain simulator). It performs no modifications, deletions, or external operations—it is a pure information query. The minimal risk reflects that status checks cannot alter system state or cause unintended consequences.
From the tool's definition Tool name 'anvil_status' and description 'Check if Anvil is running and get its status' indicate a query operation that retrieves status information without side effects.
Documented attack patterns abuse exactly the kind of access anvil_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Foundry MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for anvil_status:
{
"version": "1",
"default": "deny",
"tools": {
"anvil_status": {}
}
}anvil_status 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.
Check if Anvil is running and get its status. It is categorised as a Read tool in the Foundry MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Foundry MCP Server MCP server in PolicyLayer and add a rule for anvil_status: 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 Foundry MCP Server. Nothing to install.
anvil_status 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 anvil_status 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 anvil_status. 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.
anvil_status is provided by the Foundry MCP Server MCP server (praneshasp/foundry-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Foundry MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Foundry MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.