AI agents call get_chapter 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.
The get_chapter tool is a straightforward data retrieval function that fetches and presents chapter text from a Bible reference database. There is no indication of capability to modify, delete, execute code, or perform financial transactions. The navigation hints are purely informational. This is a classic 'Read' category tool with minimal security risk.
From the tool's definition Tool description states 'Get full chapter text with verse numbers and prev/next navigation hints' — retrieves and displays existing Bible chapter content without modification or side effects.
Attacks that exploit this kind of access
Get full chapter text with verse numbers and prev/next navigation hints. 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 get_chapter: 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.
get_chapter 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 get_chapter 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 get_chapter. 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.
get_chapter 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.
get_chapter is one line of Bible's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →