Set the conclusion (goal) to prove in the current session.
AI agents use set_conclusion to create or update resources in FOL Prover MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FOL Prover MCP Server environment.
The tool creates or modifies data within a theorem-proving session without triggering irreversible deletion, external code execution, or financial transactions. Setting a logical goal is a write operation on the session's internal state.
From the tool's definition Tool description states 'Set the conclusion (goal) to prove in the current session' — this modifies session state by writing/updating the goal parameter, which is reversible (can be changed again or cleared).
Attacks that exploit this kind of access
Set the conclusion (goal) to prove in the current session. It is categorised as a Write tool in the FOL Prover MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FOL Prover MCP Server MCP server in PolicyLayer and add a rule for set_conclusion: 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.
set_conclusion is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_conclusion 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 set_conclusion. 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.
set_conclusion 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 →