AI agents call summarize_passage to retrieve information from Bible MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and summarizes biblical passage content. It has no side effects—it does not create, modify, delete, or execute external operations. The empty description reduces confidence slightly, but the context of a Bible retrieval system and naming pattern of sibling read-only tools make it clear this is a data retrieval operation. Severity is low as misuse poses minimal risk.
From the tool's definition Tool name is 'summarize_passage' and operates within a Bible search/retrieval system that supports 'semantic search and retrieval' and 'exploration of biblical entities.' Sibling tools (lookup_passage, search_bible, search_entities, get_entity_passages) are…
Attacks that exploit this kind of access
summarize_passage. It is categorised as a Read tool in the Bible MCP MCP Server, which means it retrieves data without modifying state.
Register the Bible MCP server in PolicyLayer and add a rule for summarize_passage: 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 Bible MCP. Nothing to install.
summarize_passage 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 summarize_passage 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 summarize_passage. 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.
summarize_passage is provided by the Bible MCP server (parsifal295/bible-mcp). 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 →