Retrieve information about a specific Bitcoin Rune by name or ID (e.g., \
AI agents call rune_get to retrieve information from Satstream 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 about Bitcoin Runes (a protocol layer on Bitcoin) by name or ID. It performs no writes, deletions, executions, or financial transactions. The operation is a simple lookup/query with no state changes, placing it firmly in the Read category with low severity.
From the tool's definition Tool name 'rune_get' and description 'Retrieve information about a specific Bitcoin Rune by name or ID' indicate a query operation that fetches data without modification or side effects.
Attacks that exploit this kind of access
Retrieve information about a specific Bitcoin Rune by name or ID (e.g., \. It is categorised as a Read tool in the Satstream MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Satstream MCP Server MCP server in PolicyLayer and add a rule for rune_get: 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 Satstream MCP Server. Nothing to install.
rune_get 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 rune_get 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 rune_get. 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.
rune_get is provided by the Satstream MCP Server MCP server (satstream/ss-mcp). 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 →