AI agents call search_bible 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 performs a search operation that queries a Bible database and returns matching results. It has no side effects, cannot modify data, execute code, or trigger external operations. It is a straightforward read operation similar to a database search, presenting minimal security risk to a system.
From the tool's definition Tool description states it 'Search[es] for verses' and 'Returns matching verses with full text.' The function is purely retrieving/querying biblical text data with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Search for verses containing words or phrases. Returns matching verses with full text. Examples:. 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 search_bible: 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.
search_bible 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 search_bible 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 search_bible. 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.
search_bible is provided by the Bible MCP server (tuxr/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 →