New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_mempool_txs_by_address

Get mempool transactions for a specific address

SERVERStacks AI MCP Server SOURCEstack-ai-mcp/stacks-mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/get-mempool-txs-by-address.md

What get_mempool_txs_by_address does on Stacks AI MCP Server

AI agents call get_mempool_txs_by_address to retrieve information from Stacks AI MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_mempool_txs_by_address is rated Low

This tool retrieves or queries mempool data for informational purposes only. There are no side effects, state modifications, financial commitments, or irreversible actions. It is a standard Read operation with low severity since mempool data is public blockchain information and misuse would only affect data visibility/disclosure.

From the tool's definition Tool name 'get_mempool_txs_by_address' and description 'Get mempool transactions for a specific address' indicate a query operation that retrieves pending blockchain transaction data.

Questions about get_mempool_txs_by_address

What does the get_mempool_txs_by_address tool do? +

Get mempool transactions for a specific address. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_mempool_txs_by_address? +

Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for get_mempool_txs_by_address: 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.

What risk level is get_mempool_txs_by_address? +

get_mempool_txs_by_address is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_mempool_txs_by_address? +

Yes. Add a rate_limit block to the get_mempool_txs_by_address 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.

How do I block get_mempool_txs_by_address completely? +

Set action: deny in the PolicyLayer policy for get_mempool_txs_by_address. 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.

What MCP server provides get_mempool_txs_by_address? +

get_mempool_txs_by_address 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.

More on Stacks AI MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Stacks AI MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.