create_named_range
AI agents use create_named_range to create or update resources in Google Docs MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Docs MCP Server environment.
Named ranges in Google Docs are document structural elements that can be created and removed. This is a creation operation (Write category) rather than destructive, as it is reversible and adds metadata to documents. Confidence is slightly reduced (0.85 rather than higher) because the tool description is empty, requiring inference from the tool name and server context.
From the tool's definition Tool name 'create_named_range' indicates creation of a named range object in Google Docs. Based on server description stating 'create, read, edit, and manage Google Docs' and sibling tools like 'create_google_doc', 'create_bullet_list', 'create_folder', this…
Attacks that exploit this kind of access
create_named_range. It is categorised as a Write tool in the Google Docs MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for create_named_range: 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 Docs MCP Server. Nothing to install.
create_named_range 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 create_named_range 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 create_named_range. 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.
create_named_range is provided by the Google Docs MCP Server MCP server (nickweedon/google-docs-mcp-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →