List available theorem provers and their status.
AI agents call list_provers to retrieve information from FOL Prover MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple informational query that returns static or quasi-static data about configured provers. It has no side effects, cannot modify data, and poses minimal risk even if called by an AI agent. The tool fits the Read category: it retrieves and lists data without side effects.
From the tool's definition Tool name 'list_provers' and description 'List available theorem provers and their status' indicate a read-only query operation that retrieves information about available provers without modifying any state or executing external code.
Attacks that exploit this kind of access
List available theorem provers and their status. It is categorised as a Read tool in the FOL Prover MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FOL Prover MCP Server MCP server in PolicyLayer and add a rule for list_provers: 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.
list_provers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_provers 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.
Set action: deny in the PolicyLayer policy for list_provers. 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.
list_provers 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →