Search specifically in table headers (first row of each table).
AI agents call search_table_headers to retrieve information from DOCX-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from table headers without modifying, deleting, or executing any operations. It is a read-only search function that falls squarely into the Read category with minimal risk potential.
From the tool's definition Tool name 'search_table_headers' and description 'Search specifically in table headers (first row of each table)' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access search_table_headers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DOCX-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_table_headers:
{
"version": "1",
"default": "deny",
"tools": {
"search_table_headers": {}
}
}search_table_headers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search specifically in table headers (first row of each table). It is categorised as a Read tool in the DOCX-MCP MCP Server, which means it retrieves data without modifying state.
Register the DOCX- MCP server in PolicyLayer and add a rule for search_table_headers: 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. Nothing to install.
search_table_headers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_table_headers 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 search_table_headers. 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.
search_table_headers is provided by the DOCX- MCP server (rookie0x80/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DOCX-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 DOCX-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.