wol_get_document
AI agents call wol_get_document to retrieve information from WOL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve documents from the Watchtower Online Library based on the server's stated read-only access model and sibling tools that all perform retrieval operations. No description is provided, which slightly reduces confidence, but the context of a read-only library server and the consistent pattern of retrieval tools strongly suggests this is a document fetch operation with no side effects.
From the tool's definition Tool name 'wol_get_document' with empty description; sibling tools include 'wol_search', 'wol_browse_publications', 'wol_get_bible_text', 'wol_get_video_subtitles', and server is described as providing 'read-only access' and 'document retrieval'.
Attacks that exploit this kind of access
wol_get_document. It is categorised as a Read tool in the WOL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WOL MCP Server MCP server in PolicyLayer and add a rule for wol_get_document: 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 WOL MCP Server. Nothing to install.
wol_get_document 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 wol_get_document 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 wol_get_document. 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.
wol_get_document is provided by the WOL MCP Server MCP server (leomaiajr/wol-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →