3 tools. 3 can modify or destroy data without limits.
3 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (`decode_plantuml`, `encode_plantuml`, `generate_plantuml_diagram`) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Intercept sits between your agent and Plantuml. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @plantuml-mcp-server `decode_plantuml`:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
The Plantuml server has 3 write tools including `decode_plantuml`, `encode_plantuml`, `generate_plantuml_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.
3 tools across 1 categories: Write. 0 are read-only. 3 can modify, create, or delete data.
One line change. Instead of running the Plantuml server directly, prefix it with Intercept: intercept -c plantuml.yaml -- npx -y @plantuml-mcp-server. Download a pre-built policy from policylayer.com/policies/plantuml and adjust the limits to match your use case.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init