bible.catalog.translations
List 1000+ public-domain Bible translations across 429+ languages. Filter by ISO 639-3 language code or English name. Returns translation IDs needed for bible.passage. MIT-licensed open data (Free Use Bible API)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bible.catalog.translations.md
What bible.catalog.translations does on Apibase
AI agents call bible.catalog.translations 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 |
|---|---|---|---|
limit | integer | — | Max translations to return (default 50, max 200). |
language | string | — | Optional ISO 639-3 language code (e.g. "eng", "spa", "fra") or English language name substring (e.g. "Spanish") to filter the 1000+ translations. |
Parameters from the server's own tool schema.
Why bible.catalog.translations is rated Low
Retrieves translation metadata without side effects or data modification capabilities.
From the tool's definition List 1000+ public-domain Bible translations across 429+ languages. Filter by ISO 639-3 language code.
Attacks that exploit this kind of access
The rule that runs bible.catalog.translations 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.catalog.translations, this is the rule to start with:
bible.catalog.translations 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.catalog.translations call is checked against it from then on.
Questions about bible.catalog.translations
List 1000+ public-domain Bible translations across 429+ languages. Filter by ISO 639-3 language code or English name. Returns translation IDs needed for bible.passage. MIT-licensed open data (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.catalog.translations accepts 2 parameters: limit, language. 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.catalog.translations: 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.catalog.translations 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.catalog.translations 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.catalog.translations. 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.catalog.translations 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