sign_deploy · CSPR[dot]trade MCP: Risk & Policy

WHAT IT DOES

What sign_deploy does on CSPR[dot]trade MCP

AI agents invoke sign_deploy to trigger actions in CSPR[dot]trade MCP. 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 sign_deploy needs a policy

Although signing alone does not directly move funds, it enables execution of arbitrary blockchain transactions whose effects depend on what deploy is signed. The tool operates within a financial trading context (CSPR.trade DEX) where signed deploys directly trigger token swaps, liquidity operations, and fund transfers.

From the tool's definition The tool 'sign_deploy' performs signing of Casper blockchain deploys using local private keys (PEM files or BIP-39 mnemonics).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sign_deploy Rate-limited

sign_deploy 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": {
    "sign_deploy": {
      "limits": [
        {
          "counter": "sign_deploy_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 CSPR[dot]trade MCP, so you can run agents against it safely.

FAQ

Questions about sign_deploy

What does the sign_deploy tool do? +

Sign an unsigned Casper deploy locally. Private key never leaves this machine. Supports PEM key files and BIP-39 mnemonic phrases. It is categorised as a Execute tool in the CSPR[dot]trade MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sign_deploy? +

Register the CSPR[dot]trade MCP server in PolicyLayer and add a rule for sign_deploy: 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 CSPR[dot]trade MCP. Nothing to install.

What risk level is sign_deploy? +

sign_deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sign_deploy? +

Yes. Add a rate_limit block to the sign_deploy 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 sign_deploy completely? +

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

sign_deploy is provided by the CSPR[dot]trade MCP server (make-software/cspr-trade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.