axle_disprove · Axle MCP: Risk & Policy

WHAT IT DOES

What axle_disprove does on Axle

AI agents invoke axle_disprove to trigger actions in Axle. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why axle_disprove needs a policy

Based on the server context (AXLE CLI for Lean 4 proof engineering via remote API) and the tool name 'axle_disprove', this tool likely attempts to disprove or find counterexamples to Lean theorems by executing remote API calls. This falls under Execute as it triggers external operations. Confidence is low due to the empty description.

From the tool's definition Tool name 'axle_disprove' on a server that executes Lean 4 proof engineering via remote API. Description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

axle_disprove Rate-limited

axle_disprove stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "axle_disprove": {
      "limits": [
        {
          "counter": "axle_disprove_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Axle, so you can run agents against it safely.

FAQ

Questions about axle_disprove

What does the axle_disprove tool do? +

axle_disprove. It is categorised as a Execute tool in the Axle MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on axle_disprove? +

Register the Axle MCP server in PolicyLayer and add a rule for axle_disprove: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Axle. Nothing to install.

What risk level is axle_disprove? +

axle_disprove is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit axle_disprove? +

Yes. Add a rate_limit block to the axle_disprove rule in your PolicyLayer 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 axle_disprove completely? +

Set action: deny in the PolicyLayer policy for axle_disprove. 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 axle_disprove? +

axle_disprove is provided by the Axle MCP server (vilin97/axle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.