Sad

15 tools. 6 can modify or destroy data without limits.

6 write tools that can modify data. Rate limits recommended.

Last updated:

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

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

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

Prevents bulk unintended modifications from agents caught in loops.

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

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

How do I prevent bulk modifications through Sad? +

The Sad server has 6 write tools including bpmn_render, quiz, uml_class_diagram. 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 Sad MCP server expose? +

15 tools across 2 categories: Read, Write. 9 are read-only. 6 can modify, create, or delete data.

How do I add Intercept to my Sad setup? +

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

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.