strato.lending.safety-cooldown · Griphook MCP: Risk & Policy

WHAT IT DOES

What strato.lending.safety-cooldown does on Griphook

AI agents invoke strato.lending.safety-cooldown to trigger actions in Griphook. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why strato.lending.safety-cooldown needs a policy

Triggering a safety module cooldown is an operational action that initiates a timed process in the DeFi/lending system. This is not a simple read or write — it triggers an external protocol state change (cooldown period) that affects the user's ability to interact with the safety module (e.g., unstaking or withdrawing). It's an Execute-category action due to its side effects on the lending protocol's state.

From the tool's definition Begin safety module cooldown

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

strato.lending.safety-cooldown Rate-limited

strato.lending.safety-cooldown stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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.lending.safety-cooldown": {
      "limits": [
        {
          "counter": "strato.lending.safety-cooldown_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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.lending.safety-cooldown

What does the strato.lending.safety-cooldown tool do? +

Begin safety module cooldown. It is categorised as a Execute tool in the Griphook MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on strato.lending.safety-cooldown? +

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

strato.lending.safety-cooldown is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit strato.lending.safety-cooldown? +

Yes. Add a rate_limit block to the strato.lending.safety-cooldown 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.lending.safety-cooldown completely? +

Set action: deny in the PolicyLayer policy for strato.lending.safety-cooldown. 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.lending.safety-cooldown? +

strato.lending.safety-cooldown 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.