Get the current state of a session including all premises and conclusion.
AI agents call get_session 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 tool retrieves session information (premises and conclusion state) for inspection purposes. It has no side effects, creates no new data, executes no external operations, and makes no modifications. It is purely informational query access, making it a Read category tool with low severity risk since misuse would only expose existing session data within the theorem prover context.
From the tool's definition Tool name 'get_session' and description 'Get the current state of a session including all premises and conclusion' indicate data retrieval only.
Attacks that exploit this kind of access
Get the current state of a session including all premises and conclusion. 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 get_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.
get_session 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 get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
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 →