8 tools. 1 can modify or destroy data without limits.
1 write tool that can modify data. Rate limits recommended.
Last updated:
Write operations (generate_mermaid_graph) 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 GraphPulse C++. 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 @labsofuniverse/legacy-mcp-analyzer generate_mermaid_graph:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
analyze_codebase:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The GraphPulse C++ server has 1 write tools including generate_mermaid_graph. 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.
8 tools across 2 categories: Read, Write. 7 are read-only. 1 can modify, create, or delete data.
One line change. Instead of running the GraphPulse C++ server directly, prefix it with Intercept: intercept -c labsofuniverse-legacy-mcp-analyzer.yaml -- npx -y @labsofuniverse/legacy-mcp-analyzer. Download a pre-built policy from policylayer.com/policies/labsofuniverse-legacy-mcp-analyzer and adjust the limits to match your use case.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init