Get estimated priority fees for transactions
AI agents call getPriorityFeeEstimate 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.
This is a read-only query tool that retrieves estimated priority fee data from the Solana blockchain. It does not create, modify, delete, or execute transactions—it only provides informational estimates to help users construct transactions. No state is changed and there are no irreversible consequences from calling this tool.
From the tool's definition Tool name 'getPriorityFeeEstimate' and description 'Get estimated priority fees for transactions' indicate data retrieval with no side effects. Returns fee estimates to inform transaction construction.
Attacks that exploit this kind of access
Get estimated priority fees for transactions. 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 getPriorityFeeEstimate: 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.
getPriorityFeeEstimate 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 getPriorityFeeEstimate 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 getPriorityFeeEstimate. 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.
getPriorityFeeEstimate 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 →