Low Risk

cast_calldata_decode

Decode raw transaction calldata (with 4-byte selector) into function arguments (cast calldata-decode)

Part of the Foundry Zksync server.

cast_calldata_decode is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE FOUNDRY ZKSYNC →

Free to start. No card required.

AI agents call cast_calldata_decode to retrieve information from Foundry Zksync without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though cast_calldata_decode only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cast_calldata_decode": {}
  }
}

See the full Foundry Zksync policy for all 21 tools.

Get this rule live on your own Foundry Zksync server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FOUNDRY ZKSYNC →

View all 21 tools →

These attack patterns abuse exactly the kind of access cast_calldata_decode gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so cast_calldata_decode only ever does what you allow.

SECURE FOUNDRY ZKSYNC →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the cast_calldata_decode tool do? +

Decode raw transaction calldata (with 4-byte selector) into function arguments (cast calldata-decode). It is categorised as a Read tool in the Foundry Zksync MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cast_calldata_decode? +

Register the Foundry Zksync MCP server in PolicyLayer and add a rule for cast_calldata_decode: 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 Zksync. Nothing to install.

What risk level is cast_calldata_decode? +

cast_calldata_decode is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cast_calldata_decode? +

Yes. Add a rate_limit block to the cast_calldata_decode 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 cast_calldata_decode completely? +

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

cast_calldata_decode is provided by the Foundry Zksync MCP server (foundry-zksync-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Foundry Zksync tool call.

Deterministic rules across all 21 Foundry Zksync tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.