search_by_id

Search blocks, transactions, contracts, or accounts by hash/ID

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/search-by-id.md

WHAT IT DOES

What search_by_id does on Stacks AI MCP Server

AI agents call search_by_id 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.

RISK

Why search_by_id is rated Low

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

RECOMMENDED RULE

The rule that runs search_by_id safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Stacks AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_by_id, this is the rule to start with:

search_by_id Allowed

search_by_id is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_by_id": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stacks AI MCP Server, apply this rule, and every search_by_id call is checked against it from then on.

FAQ

Questions about search_by_id

What does the search_by_id tool do? +

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.

How do I enforce a policy on search_by_id? +

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.

What risk level is search_by_id? +

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

Can I rate-limit search_by_id? +

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.

How do I block search_by_id completely? +

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.

What MCP server provides search_by_id? +

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.

KEEP EXPLORING

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

This server

All 200 Stacks AI MCP Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →