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