AI agents call bible_search 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 retrieves and queries Bible verse data locally. It has no side effects, does not execute code, does not modify data, and does not create financial obligations. The search functionality is a standard read-only operation. Even with optional parameters (book limiting, result count), the action remains informational lookup only.
From the tool's definition Tool description states 'Search for text within a Bible version' and 'Performs case-insensitive substring matching across all verses.' These are purely data retrieval operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search for text within a Bible version. Performs case-insensitive substring matching across all verses. Optionally limit to a specific book and set a max number of results. 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_search: 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_search 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_search 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_search. 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_search 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 →