Critical Risk →

clear_table_structure_cache

清空表格结构缓存

How to control clear_table_structure_cache ↓

AI agents call clear_table_structure_cache to permanently remove resources in Docx_MCP_cj — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

The tool clears/purges a cache of table structure data. Clearing a cache is an irreversible operation (the cached data is lost), making it Destructive. However, since caches are typically rebuildable from source data, the blast radius is medium rather than high — it may cause performance degradation or require re-analysis of documents but doesn't destroy primary data.

From the tool's definition 清空表格结构缓存 (Clear/empty table structure cache)

Documented attack patterns abuse exactly the kind of access clear_table_structure_cache gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Docx_MCP_cj, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_table_structure_cache:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_table_structure_cache"
  ]
}

clear_table_structure_cache disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Docx_MCP_cj — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the clear_table_structure_cache tool do? +

清空表格结构缓存. It is categorised as a Destructive tool in the Docx_MCP_cj MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_table_structure_cache? +

Register the Docx_MCP_cj MCP server in PolicyLayer and add a rule for clear_table_structure_cache: 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 Docx_MCP_cj. Nothing to install.

What risk level is clear_table_structure_cache? +

clear_table_structure_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_table_structure_cache? +

Yes. Add a rate_limit block to the clear_table_structure_cache 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.

How do I block clear_table_structure_cache completely? +

Set action: deny in the PolicyLayer policy for clear_table_structure_cache. 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.

What MCP server provides clear_table_structure_cache? +

clear_table_structure_cache is provided by the Docx_MCP_cj MCP server (rockcj/docx_mcp_cj). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Docx_MCP_cj tool call.

Deterministic rules across all 54 Docx_MCP_cj tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

54 Docx_MCP_cj tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.