convert_document
Convert a document to another format using LibreOffice
This record as markdown: /tools/jrmatherly-mcp-context-forge/convert-document.md
What convert_document does on ContextForge MCP Gateway
AI agents use convert_document to create or update resources in ContextForge MCP Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ContextForge MCP Gateway environment.
Why convert_document is rated Medium
Converting a document to another format constitutes a write operation—it creates new data (the converted document) in a different format. While the original may remain unchanged, the tool produces new artifacts. This is reversible (the original can still be converted again), so it does not rise to Destructive level.
From the tool's definition Tool name 'convert_document' and description 'Convert a document to another format using LibreOffice' indicate the tool modifies or transforms document formats, creating output in a new format.
Attacks that exploit this kind of access
The rule that runs convert_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convert_document, this is the rule to start with:
convert_document stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every convert_document call is checked against it from then on.
Questions about convert_document
Convert a document to another format using LibreOffice. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for convert_document: 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 ContextForge MCP Gateway. Nothing to install.
convert_document 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_document 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_document. 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_document is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ContextForge MCP Gateway, and thousands of servers like it.
This server
Across the catalogue