Batch data cleaning operations with intelligent detection of common data quality issues
AI agents use data_cleaner to create or update resources in Excel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Excel MCP Server environment.
Data cleaning modifies data by correcting, normalizing, or removing entries with quality issues. This is a reversible write operation (data is altered/updated) but not inherently destructive in the sense of permanently deleting records. The 'batch' nature increases blast radius since it can affect many records at once, warranting medium severity.
From the tool's definition Batch data cleaning operations with intelligent detection of common data quality issues
Documented attack patterns abuse exactly the kind of access data_cleaner gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Excel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for data_cleaner:
{
"version": "1",
"default": "deny",
"tools": {
"data_cleaner": {
"limits": [
{
"counter": "data_cleaner_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} data_cleaner 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.
Batch data cleaning operations with intelligent detection of common data quality issues. It is categorised as a Write tool in the Excel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Excel MCP Server MCP server in PolicyLayer and add a rule for data_cleaner: 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 Excel MCP Server. Nothing to install.
data_cleaner 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 data_cleaner 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 data_cleaner. 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.
data_cleaner is provided by the Excel MCP Server MCP server (ishayoyo/excel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Excel 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.
35 Excel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.