AI agents invoke excel_to_json to trigger actions in PDF Co MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the tool name alone, this likely converts an Excel file to JSON format, which is a data transformation/processing operation. Given the server context (PDF.co API for document processing), this is most likely a Read/Execute type operation that processes/transforms a file. With no description available, confidence is low.
From the tool's definition Tool name is 'excel_to_json'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access excel_to_json 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_json:
{
"version": "1",
"default": "deny",
"tools": {
"excel_to_json": {
"limits": [
{
"counter": "excel_to_json_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}excel_to_json stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
excel_to_json. It is categorised as a Execute tool in the PDF Co MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PDF Co MCP Server MCP server in PolicyLayer and add a rule for excel_to_json: 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_json is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the excel_to_json 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_json. 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_json 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.