Make a custom smart contract that represents an account that can be deployed and interacted with other contracts, and can be extended to implement custom logic. An account is a special type of contract that is used to validate and execute transactions. Returns the source code of the generated con...
Risk signalsHigh parameter count (12 properties)
Part of the Contracts server.
Free to start. No card required.
AI agents invoke cairo-account to trigger processes or run actions in Contracts. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
cairo-account can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"cairo-account": {
"limits": [
{
"counter": "cairo-account_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Contracts policy for all 25 tools.
These attack patterns abuse exactly the kind of access cairo-account gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Make a custom smart contract that represents an account that can be deployed and interacted with other contracts, and can be extended to implement custom logic. An account is a special type of contract that is used to validate and execute transactions. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.. It is categorised as a Execute tool in the Contracts MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Contracts MCP server in PolicyLayer and add a rule for cairo-account: 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 Contracts. Nothing to install.
cairo-account is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cairo-account 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 cairo-account. 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.
cairo-account is provided by the Contracts MCP server (@openzeppelin/contracts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Contracts 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.