AI agents use aptos_abi_generate to create or update resources in Aptos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aptos environment.
An AI agent can call aptos_abi_generate faster than any human can review — one bad instruction and it creates or modifies resources in Aptos by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Generate ABI for an Aptos contract. It is categorised as a Write tool in the Aptos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aptos MCP server in PolicyLayer and add a rule for aptos_abi_generate: 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 Aptos. Nothing to install.
aptos_abi_generate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the aptos_abi_generate 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 aptos_abi_generate. 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.
aptos_abi_generate is provided by the Aptos MCP server (tlazypanda/aptos-mcp-server). 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 →