Get a complete ready-to-compile Chimera project template for a standard protocol type.
AI agents call get_template to retrieve information from Recon Fuzz Chimera without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns a pre-built project template for fuzzing Solidity smart contracts. It is purely informational/data retrieval with no side effects, no code execution, and no modifications to persistent state. The template is provided for local use by the developer. This is a standard Read operation.
From the tool's definition Tool description indicates 'Get a complete ready-to-compile Chimera project template' - a retrieval operation that provides template data without modifying any system state or executing external code.
Attacks that exploit this kind of access
Get a complete ready-to-compile Chimera project template for a standard protocol type. It is categorised as a Read tool in the Recon Fuzz Chimera MCP Server, which means it retrieves data without modifying state.
Register the Recon Fuzz Chimera MCP server in PolicyLayer and add a rule for get_template: 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 Recon Fuzz Chimera. Nothing to install.
get_template 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 get_template 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 get_template. 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.
get_template is provided by the Recon Fuzz Chimera MCP server (recon-fuzz/recon-mcp-chimera). 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 →