Create a new named session for proof building.
AI agents use create_session 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.
This tool creates a new session, which is a reversible write operation—sessions can be deleted or cleared. It does not execute arbitrary code, delete data, move money, or cause irreversible harm. The operation is limited in scope (session metadata creation) and poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'create_session' and description 'Create a new named session for proof building' indicate creation of a new session object/record.
Attacks that exploit this kind of access
Create a new named session for proof building. 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 create_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.
create_session 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 create_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 create_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.
create_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 →