strato.bridge.request-withdrawal

WHAT IT DOES

What strato.bridge.request-withdrawal does on Griphook

AI agents use strato.bridge.request-withdrawal to commit financial operations through Griphook — usually the final step of a payment, billing, or trading workflow. A call moves real money.

WHY IT NEEDS A POLICY

Why strato.bridge.request-withdrawal needs a policy

This tool initiates a cross-chain withdrawal, which moves assets from the STRATO blockchain to an external chain. This constitutes a financial operation with potentially irreversible asset movement across chains, making it Financial category with high severity due to the blast radius of misdirected or unauthorized withdrawals.

From the tool's definition Submit a withdrawal request to an external chain

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

strato.bridge.request-withdrawal Approval-gated

Any call to strato.bridge.request-withdrawal is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "strato.bridge.request-withdrawal": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE 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.bridge.request-withdrawal

What does the strato.bridge.request-withdrawal tool do? +

Submit a withdrawal request to an external chain. It is categorised as a Financial tool in the Griphook MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on strato.bridge.request-withdrawal? +

Register the Griphook MCP server in PolicyLayer and add a rule for strato.bridge.request-withdrawal: 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.bridge.request-withdrawal? +

strato.bridge.request-withdrawal is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit strato.bridge.request-withdrawal? +

Yes. Add a rate_limit block to the strato.bridge.request-withdrawal 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.bridge.request-withdrawal completely? +

Set action: deny in the PolicyLayer policy for strato.bridge.request-withdrawal. 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.bridge.request-withdrawal? +

strato.bridge.request-withdrawal 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.