get_reading_time

Estimate reading time for the open document.

SERVERDocx SOURCEsecurityronin/docx-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/get-reading-time.md

WHAT IT DOES

What get_reading_time does on Docx

AI agents call get_reading_time 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.

RISK

Why get_reading_time is rated Low

This tool queries document properties to calculate an estimate—a passive retrieval operation with no side effects. It fits the 'Read' category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because misuse cannot harm data integrity or trigger unintended operations.

From the tool's definition Tool name 'get_reading_time' and description 'Estimate reading time for the open document' indicate a read-only operation that retrieves metadata about document content without modifying, executing, or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_reading_time 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 get_reading_time, this is the rule to start with:

get_reading_time Allowed

get_reading_time is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_reading_time": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every get_reading_time call is checked against it from then on.

FAQ

Questions about get_reading_time

What does the get_reading_time tool do? +

Estimate reading time for the open document. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_reading_time? +

Register the Docx MCP server in PolicyLayer and add a rule for get_reading_time: 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.

What risk level is get_reading_time? +

get_reading_time is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_reading_time? +

Yes. Add a rate_limit block to the get_reading_time 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 get_reading_time completely? +

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

get_reading_time 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.

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 219 Docx tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →