AI agents use excel_to_txt to create or update resources in PDF Co MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF Co MCP Server environment.
Based on the naming pattern consistent with sibling tools (excel_to_csv, excel_to_html, excel_to_json, excel_to_pdf, excel_to_xml), this tool likely converts Excel files to plain text format. Conversion tools typically read input and write/create a new output file, placing it in the Write category. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'excel_to_txt' suggests a conversion operation; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access excel_to_txt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PDF Co MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for excel_to_txt:
{
"version": "1",
"default": "deny",
"tools": {
"excel_to_txt": {
"limits": [
{
"counter": "excel_to_txt_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}excel_to_txt 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.
Free to start. No card required.
excel_to_txt. It is categorised as a Write tool in the PDF Co MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PDF Co MCP Server MCP server in PolicyLayer and add a rule for excel_to_txt: 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 PDF Co MCP Server. Nothing to install.
excel_to_txt 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 excel_to_txt 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 excel_to_txt. 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.
excel_to_txt is provided by the PDF Co MCP Server MCP server (pdfdotco/pdfco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PDF Co MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 PDF Co MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.