Convert a FOL problem to TPTP format (standard format for theorem provers).
AI agents use convert_to_tptp 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 takes existing FOL problem data and converts it to a different format (TPTP). This is a reversible transformation—the original data is not destroyed, and the operation is primarily about representation rather than execution of external code or deletion.
From the tool's definition Tool converts a FOL problem to TPTP format. The description indicates it transforms/formats data ('Convert a FOL problem to TPTP format'), which is a data transformation operation.
Attacks that exploit this kind of access
Convert a FOL problem to TPTP format (standard format for theorem provers). 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 convert_to_tptp: 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.
convert_to_tptp 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 convert_to_tptp 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 convert_to_tptp. 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.
convert_to_tptp 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 →