AI agents call strato.swap 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.
The description uses only read-oriented verbs ('Inspect') and lists informational data retrieval actions (pools, tokens, LP positions, history, details). No mutations, executions, or financial transactions are indicated.
From the tool's definition Inspect swap pools, supported tokens, LP positions, history, and specific pool details
Attacks that exploit this kind of access
Inspect swap pools, supported tokens, LP positions, history, and specific pool details. 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.swap: 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.swap 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.swap 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.swap. 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.swap 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 →