AI agents call bible_list_versions 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 enumerates metadata about available Bible translations. It is purely informational with no side effects, no code execution, and no data modification. The optional language filter is a read-only parameter. Misuse would have minimal blast radius.
From the tool's definition Tool lists available Bible versions; the description indicates a query/retrieval action ('List all available Bible versions') with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
List all available Bible versions. Optionally filter by language code (e.g. 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_versions: 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_versions 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_versions 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_versions. 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_versions 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 →