AI agents use set_data_validation to create or update resources in Office Editor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Office Editor environment.
Data validation setup modifies spreadsheet properties to restrict or validate cell inputs, but does not delete data or execute arbitrary code. This is a reversible modification (Write category).
From the tool's definition Tool name 'set_data_validation' indicates modification of spreadsheet validation rules. Server context shows this is an office document editor (Word, Excel, PowerPoint).
Documented attack patterns abuse exactly the kind of access set_data_validation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Office Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for set_data_validation:
{
"version": "1",
"default": "deny",
"tools": {
"set_data_validation": {
"limits": [
{
"counter": "set_data_validation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_data_validation 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.
set_data_validation. It is categorised as a Write tool in the Office Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Office Editor MCP server in PolicyLayer and add a rule for set_data_validation: 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 Office Editor. Nothing to install.
set_data_validation 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 set_data_validation 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 set_data_validation. 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.
set_data_validation is provided by the Office Editor MCP server (thewdy/office-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 Office Editor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 Office Editor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.