generate_properties · Recon Fuzz Chimera MCP: Risk & Policy

WHAT IT DOES

What generate_properties does on Recon Fuzz Chimera

AI agents use generate_properties to create or update resources in Recon Fuzz Chimera — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Recon Fuzz Chimera environment.

WHY IT NEEDS A POLICY

Why generate_properties needs a policy

The tool creates new Solidity code structures (skeletons) and property definitions that would be written to the user's project. This is a Write operation—it produces and outputs new data/code. It does not execute contracts, delete data, or move funds.

From the tool's definition Tool generates 'Solidity skeletons' and creates 'invariant properties' as artifacts. While no data is explicitly deleted or permanently overwritten, the generation of code templates and scaffolding represents creation/modification of development artifacts.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_properties Rate-limited

generate_properties 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_properties": {
      "limits": [
        {
          "counter": "generate_properties_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Recon Fuzz Chimera, so you can run agents against it safely.

FAQ

Questions about generate_properties

What does the generate_properties tool do? +

Generate 8-15 curated invariant properties with Solidity skeletons based on the protocol type and contract source. It is categorised as a Write tool in the Recon Fuzz Chimera MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_properties? +

Register the Recon Fuzz Chimera MCP server in PolicyLayer and add a rule for generate_properties: 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.

What risk level is generate_properties? +

generate_properties is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_properties? +

Yes. Add a rate_limit block to the generate_properties 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.

How do I block generate_properties completely? +

Set action: deny in the PolicyLayer policy for generate_properties. 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.

What MCP server provides generate_properties? +

generate_properties 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.