AI agents use strato.swap.create-pool to create or update resources in Griphook — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Griphook environment.
This tool creates new on-chain liquidity pools, which modifies blockchain state irreversibly in the sense that the pool's creation record is immutable, but the tool itself does not delete data or execute arbitrary code. While it has financial implications (pool creation affects DeFi ecosystem liquidity and can incur gas fees), the primary action is data creation rather than money movement.
From the tool's definition Tool name 'strato.swap.create-pool' and description 'Create a new swap pool between tokenA and tokenB' indicates creation of a new asset/liquidity pool on a blockchain DeFi platform.
Attacks that exploit this kind of access
Create a new swap pool between tokenA and tokenB. It is categorised as a Write tool in the Griphook MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Griphook MCP server in PolicyLayer and add a rule for strato.swap.create-pool: 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.create-pool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the strato.swap.create-pool 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.create-pool. 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.create-pool 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 →