prove_session · FOL Prover MCP Server MCP: Risk & Policy

WHAT IT DOES

What prove_session does on FOL Prover MCP Server

AI agents invoke prove_session to trigger actions in FOL Prover MCP Server. 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 prove_session needs a policy

This tool executes external prover processes whose behavior depends on the formulas and premises in the current session. While theorem proving itself is deterministic and non-destructive, the 'Execute' category applies because the tool runs code/external operations whose effects depend on arguments (the session's formulas and premises).

From the tool's definition Tool name 'prove_session' and description 'Execute a proof using the current session' directly indicate code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

prove_session Rate-limited

prove_session 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": {
    "prove_session": {
      "limits": [
        {
          "counter": "prove_session_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 FOL Prover MCP Server, so you can run agents against it safely.

FAQ

Questions about prove_session

What does the prove_session tool do? +

Execute a proof using the current session. It is categorised as a Execute tool in the FOL Prover MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on prove_session? +

Register the FOL Prover MCP Server MCP server in PolicyLayer and add a rule for prove_session: 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 FOL Prover MCP Server. Nothing to install.

What risk level is prove_session? +

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

Can I rate-limit prove_session? +

Yes. Add a rate_limit block to the prove_session 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 prove_session completely? +

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

prove_session is provided by the FOL Prover MCP Server MCP server (newjerseystyle/folprover-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.