AI agents call clear_conditional_formatting to permanently remove resources in Office Editor — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The word 'clear' strongly suggests irreversible removal of conditional formatting from a document. While not catastrophic (data itself is not deleted, only formatting rules), this action is likely not easily reversible once applied. Empty description lowers confidence. Given sibling tools like 'add_conditional_formatting', this tool likely removes what those tools create.
From the tool's definition Tool name 'clear_conditional_formatting' implies removing/deleting conditional formatting rules; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access clear_conditional_formatting 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 clear_conditional_formatting:
{
"version": "1",
"default": "deny",
"hide": [
"clear_conditional_formatting"
]
}clear_conditional_formatting disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
clear_conditional_formatting. It is categorised as a Destructive tool in the Office Editor MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Office Editor MCP server in PolicyLayer and add a rule for clear_conditional_formatting: 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.
clear_conditional_formatting is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_conditional_formatting 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 clear_conditional_formatting. 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.
clear_conditional_formatting 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.