AI agents call strato.events to retrieve information from Griphook without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or searches chain events data from a blockchain platform without any indication of side effects, data modification, or state changes. It is a passive query operation against a backend search interface, fitting the definition of 'Read' category. The low severity reflects that querying blockchain events poses minimal risk of unintended harm when invoked by an AI agent.
From the tool's definition Tool name 'strato.events' with description 'Query chain events through the backend search interface' uses the verb 'query' which is a read-only operation. No modification, deletion, execution, or financial commitment is described.
Attacks that exploit this kind of access
Query chain events through the backend search interface. It is categorised as a Read tool in the Griphook MCP Server, which means it retrieves data without modifying state.
Register the Griphook MCP server in PolicyLayer and add a rule for strato.events: 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 Griphook. Nothing to install.
strato.events 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 strato.events 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 strato.events. 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.
strato.events is provided by the Griphook MCP server (strato-net/strato-griphook). 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 →