get_mempool_info
Get pending transactions in the mempool.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/get-mempool-info.md
What get_mempool_info does on Aibtc
AI agents call get_mempool_info to retrieve information from Aibtc 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_info is rated Low
This tool queries blockchain mempool state to retrieve information about pending transactions. It has no side effects, does not modify data, and does not execute transactions or commands. It is a straightforward information retrieval operation, making it a Read category tool with low severity risk.
From the tool's definition Tool name and description indicate retrieval of mempool data: 'Get pending transactions in the mempool.' The verb 'Get' and the read-only nature of querying pending transaction information without modifying state confirms this is a data retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_mempool_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_mempool_info, this is the rule to start with:
get_mempool_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every get_mempool_info call is checked against it from then on.
Questions about get_mempool_info
Get pending transactions in the mempool. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for get_mempool_info: 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 Aibtc. Nothing to install.
get_mempool_info 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_mempool_info 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_mempool_info. 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_mempool_info is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue