strato.swap.remove-liquidity · Griphook MCP: Risk & Policy

WHAT IT DOES

What strato.swap.remove-liquidity does on Griphook

AI agents use strato.swap.remove-liquidity 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.

WHY IT NEEDS A POLICY

Why strato.swap.remove-liquidity needs a policy

Removing liquidity from a DeFi pool is a Write operation because it modifies data (LP token balance, pool composition) reversibly. While it involves financial assets, the operation itself is not a direct movement of value between parties (which would be Financial); rather, it's withdrawal of the user's own capital from a pool.

From the tool's definition Tool name 'strato.swap.remove-liquidity' and description 'Redeem LP tokens from a pool' indicates the tool modifies liquidity pool state by removing the user's liquidity position.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

strato.swap.remove-liquidity Rate-limited

strato.swap.remove-liquidity stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "strato.swap.remove-liquidity": {
      "limits": [
        {
          "counter": "strato.swap.remove-liquidity_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Griphook, so you can run agents against it safely.

FAQ

Questions about strato.swap.remove-liquidity

What does the strato.swap.remove-liquidity tool do? +

Redeem LP tokens from a pool. 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.

How do I enforce a policy on strato.swap.remove-liquidity? +

Register the Griphook MCP server in PolicyLayer and add a rule for strato.swap.remove-liquidity: 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.

What risk level is strato.swap.remove-liquidity? +

strato.swap.remove-liquidity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit strato.swap.remove-liquidity? +

Yes. Add a rate_limit block to the strato.swap.remove-liquidity 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.

How do I block strato.swap.remove-liquidity completely? +

Set action: deny in the PolicyLayer policy for strato.swap.remove-liquidity. 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.

What MCP server provides strato.swap.remove-liquidity? +

strato.swap.remove-liquidity 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.