Get transactions that were dropped from mempool
AI agents call get_dropped_mempool_txs to retrieve information from Stacks AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical or status information about transactions that failed to confirm and were removed from the mempool. It is purely informational—querying blockchain state without side effects. No funds are moved, data is not modified, code is not executed, and no operations are triggered. This is a straightforward Read operation with minimal blast radius if misused.
From the tool's definition Tool name 'get_dropped_mempool_txs' and description 'Get transactions that were dropped from mempool' indicate a retrieval operation with no modification or execution of blockchain operations.
Attacks that exploit this kind of access
Get transactions that were dropped from mempool. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for get_dropped_mempool_txs: 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 Stacks AI MCP Server. Nothing to install.
get_dropped_mempool_txs 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 get_dropped_mempool_txs 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 get_dropped_mempool_txs. 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.
get_dropped_mempool_txs is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-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 →