Spinnaker

37 tools. 9 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated:

9 can modify or destroy data
28 read-only
37 tools total
Read (28) Write / Execute (6) Destructive / Financial (3)

Destructive tools (cancel_execution, delete_pipeline, delete_strategy) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (resume_execution, save_pipeline, save_strategy) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (restart_stage, trigger_pipeline) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

Deny destructive operations
cancel_execution:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
resume_execution:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
evaluate_expression:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Can an AI agent delete data through the Spinnaker MCP server? +

Yes. The Spinnaker server exposes 3 destructive tools including cancel_execution, delete_pipeline, delete_strategy. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Spinnaker? +

The Spinnaker server has 4 write tools including resume_execution, save_pipeline, save_strategy. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Spinnaker MCP server expose? +

37 tools across 4 categories: Destructive, Execute, Read, Write. 28 are read-only. 9 can modify, create, or delete data.

How do I add Intercept to my Spinnaker setup? +

One line change. Instead of running the Spinnaker server directly, prefix it with Intercept: intercept -c io-github-geiserx-spinnaker-mcp.yaml -- npx -y @spinnaker-mcp. Download a pre-built policy from policylayer.com/policies/io-github-geiserx-spinnaker-mcp and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.