Search blocks, transactions, contracts, or accounts by hash/ID
AI agents call search_by_id 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 blockchain data (blocks, transactions, contracts, accounts) based on identifiers. It performs lookups and queries with no side effects, no code execution, and no state changes. This is a straightforward Read operation with minimal risk in a DeFi context—it merely surfaces publicly available blockchain information.
From the tool's definition Tool name 'search_by_id' and description 'Search blocks, transactions, contracts, or accounts by hash/ID' indicate data retrieval operations without modification or execution capabilities.
Attacks that exploit this kind of access
Search blocks, transactions, contracts, or accounts by hash/ID. 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 search_by_id: 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.
search_by_id 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 search_by_id 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 search_by_id. 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.
search_by_id 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 →