Medium Risk

disableAuth

Toggle authentication on Uptime Kuma

Can disable authentication entirely

Part of the Mcp Uptime Kuma MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use disableAuth to create or modify resources in Mcp Uptime Kuma. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call disableAuth repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Uptime Kuma.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-davidfuchs-mcp-uptime-kuma.yaml
tools:
  disableAuth:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mcp Uptime Kuma policy for all 18 tools.

Tool Name disableAuth
Category Write
Risk Level Medium

View all 18 tools →

Agents calling write-class tools like disableAuth have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the disableAuth tool do? +

Toggle authentication on Uptime Kuma. It is categorised as a Write tool in the Mcp Uptime Kuma MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disableAuth? +

Add a rule in your Intercept YAML policy under the tools section for disableAuth. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Uptime Kuma MCP server.

What risk level is disableAuth? +

disableAuth is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disableAuth? +

Yes. Add a rate_limit block to the disableAuth rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block disableAuth completely? +

Set action: deny in the Intercept policy for disableAuth. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides disableAuth? +

disableAuth is provided by the Mcp Uptime Kuma MCP server (@davidfuchs/mcp-uptime-kuma). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Uptime Kuma

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.