check_accessibility
Scan the document for accessibility issues.
This record as markdown: /tools/securityronin-docx-mcp/check-accessibility.md
What check_accessibility does on Docx
AI agents call check_accessibility to retrieve information from Docx without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_accessibility is rated Low
This tool performs document analysis and validation (checking for accessibility issues) without creating, modifying, deleting, or executing any operations with side effects. It is purely informational and fits the Read category. The severity is low because accessibility scanning has no blast radius—it cannot harm the document, financial systems, or external operations.
From the tool's definition The tool description states it 'Scan[s] the document for accessibility issues' — a scanning/auditing operation that retrieves information about the document without modifying it.
Attacks that exploit this kind of access
The rule that runs check_accessibility safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_accessibility, this is the rule to start with:
check_accessibility is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every check_accessibility call is checked against it from then on.
Questions about check_accessibility
Scan the document for accessibility issues. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.
Register the Docx MCP server in PolicyLayer and add a rule for check_accessibility: 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. Nothing to install.
check_accessibility 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 check_accessibility 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 check_accessibility. 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.
check_accessibility is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docx, and thousands of servers like it.
This server
Across the catalogue