wol_browse_publications
AI agents call wol_browse_publications 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 browses publications within a read-only library system. Browsing is a retrieval operation with no side effects—it queries and presents data without creating, modifying, deleting, or executing anything.
From the tool's definition Server description states 'read-only access' and 'search and browse Jehovah's Witnesses publications'. Tool name 'wol_browse_publications' indicates browsing/retrieval of publication data with no modification capabilities.
Attacks that exploit this kind of access
wol_browse_publications. 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_browse_publications: 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_browse_publications 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_browse_publications 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_browse_publications. 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_browse_publications 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 →