AI agents call bible_compare to retrieve information from Bible without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and displays data (Bible verses) in different formats without creating, modifying, or deleting any information. It is a read-only comparison operation consistent with the server's stated purpose of enabling 'AI assistants to look up Bible verses' locally. No side effects or state changes occur.
From the tool's definition Tool enables looking up and comparing Bible verses across translations. Description states it retrieves passages 'to see how each translation renders that passage side by side' with no mention of modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Compare the same verse across multiple Bible versions. Provide a book, chapter, verse reference and a list of versions to see how each translation renders that passage side by side. It is categorised as a Read tool in the Bible MCP Server, which means it retrieves data without modifying state.
Register the Bible MCP server in PolicyLayer and add a rule for bible_compare: 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. Nothing to install.
bible_compare 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 bible_compare 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 bible_compare. 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.
bible_compare is provided by the Bible MCP server (stackpwnies/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 →