Add data validation rules to a sheet range
AI agents use addDataValidation to create or update resources in Google Drive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive MCP Server environment.
This tool modifies spreadsheet properties (data validation rules) but does not delete data, execute arbitrary code, or cause destructive effects. It is categorized as Write because it creates or modifies spreadsheet metadata/configurations reversibly.
From the tool's definition Tool name 'addDataValidation' and description 'Add data validation rules to a sheet range' indicate modification of spreadsheet configurations. This creates or modifies validation rules on existing data ranges, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access addDataValidation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Drive MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for addDataValidation:
{
"version": "1",
"default": "deny",
"tools": {
"addDataValidation": {
"limits": [
{
"counter": "adddatavalidation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} addDataValidation 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.
Add data validation rules to a sheet range. It is categorised as a Write tool in the Google Drive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for addDataValidation: 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 Google Drive MCP Server. Nothing to install.
addDataValidation 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 addDataValidation 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 addDataValidation. 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.
addDataValidation is provided by the Google Drive MCP Server MCP server (piotr-agier/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 107 Google Drive MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
107 Google Drive MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.