Lists all transactions that have involved the given inscription, starting from its origin (reveal transaction) and including all transfers.
AI agents call activity_by_inscription to retrieve information from Maestro 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 and displays historical blockchain data about an inscription's transaction activity. It performs a read-only query operation on the Bitcoin blockchain without modifying, executing arbitrary code, deleting, or moving funds. The low severity reflects that unauthorized access only exposes historical transaction information already visible on a public blockchain.
From the tool's definition Tool 'activity_by_inscription' with description 'Lists all transactions that have involved the given inscription, starting from its origin (reveal transaction) and including all transfers.' — the verb 'Lists' and action of retrieving historical transaction…
Documented attack patterns abuse exactly the kind of access activity_by_inscription gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Maestro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for activity_by_inscription:
{
"version": "1",
"default": "deny",
"tools": {
"activity_by_inscription": {}
}
} activity_by_inscription is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists all transactions that have involved the given inscription, starting from its origin (reveal transaction) and including all transfers. It is categorised as a Read tool in the Maestro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Maestro MCP Server MCP server in PolicyLayer and add a rule for activity_by_inscription: 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 Maestro MCP Server. Nothing to install.
activity_by_inscription 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 activity_by_inscription 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 activity_by_inscription. 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.
activity_by_inscription is provided by the Maestro MCP Server MCP server (maestro-org/maestro-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Maestro MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
117 Maestro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.