Simulate a transaction to get the total compute units consumed
AI agents call getComputeUnits to retrieve information from AMOCA Solana MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only simulation to estimate resource consumption. It does not execute transactions, modify wallet state, move funds, or trigger irreversible actions. The word 'simulate' indicates no actual blockchain state change occurs. This is informational data retrieval about transaction costs, analogous to a gas estimation function.
From the tool's definition Tool description states 'Simulate a transaction to get the total compute units consumed' — this is a simulation/query operation that retrieves computational cost data without executing any actual transaction or modifying state on-chain.
Attacks that exploit this kind of access
Simulate a transaction to get the total compute units consumed. It is categorised as a Read tool in the AMOCA Solana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AMOCA Solana MCP Server MCP server in PolicyLayer and add a rule for getComputeUnits: 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 AMOCA Solana MCP Server. Nothing to install.
getComputeUnits 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 getComputeUnits 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 getComputeUnits. 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.
getComputeUnits is provided by the AMOCA Solana MCP Server MCP server (manolaz/amoca-solana-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 →