bible.text.passage
Fetch the verse-by-verse text of a Bible chapter for a given translation and book (e.g. KJV / John / 3). Returns array of {number, text}. Free Use Bible API
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bible.text.passage.md
What bible.text.passage does on Apibase
AI agents call bible.text.passage to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
book | string | Yes | Book ID — typically a 3-letter code (e.g. "GEN", "JHN", "PSA") or full name. Use bible.books to discover. |
chapter | integer | Yes | Chapter number (1-based, e.g. 3 for John 3). |
translation | string | Yes | Bible translation ID (e.g. "KJV", "ASV", "WEB", "BSB"). |
Parameters from the server's own tool schema.
Why bible.text.passage is rated Low
Retrieves static Bible passage text with no side effects or data modification.
From the tool's definition Fetch the verse-by-verse text of a Bible chapter
Attacks that exploit this kind of access
The rule that runs bible.text.passage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bible.text.passage, this is the rule to start with:
bible.text.passage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every bible.text.passage call is checked against it from then on.
Questions about bible.text.passage
Fetch the verse-by-verse text of a Bible chapter for a given translation and book (e.g. KJV / John / 3). Returns array of {number, text}. Free Use Bible API. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
bible.text.passage accepts 3 parameters: book, chapter, translation. Required: book, chapter, translation. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for bible.text.passage: 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 Apibase. Nothing to install.
bible.text.passage 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.text.passage 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.text.passage. 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.text.passage is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue