AI agents call bible_list_books 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 is a straightforward query/list operation that retrieves metadata about available books in a Bible version. There is no capability to modify data, execute code, delete resources, or perform financial transactions. The blast radius of misuse is negligible—returning book names poses no security risk.
From the tool's definition Tool name 'bible_list_books' and description 'List all books available' indicate a retrieval operation with no side effects. Returns book names without modification, creation, deletion, or execution of external operations.
Attacks that exploit this kind of access
List all books available in a specific Bible version. Returns book names as they appear in that version (may be in the original language for non-English versions). 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_list_books: 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_list_books 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_list_books 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_list_books. 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_list_books 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 →