format_matching_text
AI agents use format_matching_text 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.
The tool modifies document content by applying formatting to matching text, which is a reversible write operation. No description provided reduces confidence slightly. Severity is medium because formatting changes are non-destructive but could affect document appearance and readability if misapplied at scale.
From the tool's definition Tool name 'format_matching_text' and server description stating 'edit...with support for formatting'; sibling tools include 'apply_paragraph_style' and 'apply_text_style' indicating formatting operations.
Attacks that exploit this kind of access
format_matching_text. 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 format_matching_text: 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.
format_matching_text 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 format_matching_text 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 format_matching_text. 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.
format_matching_text 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 →