Free-form natural-language search across all Bible chunks, ranked by cosine similarity. Each result includes the top-N pre-computed Urantia paragraphs related to that chunk via bible_parallels (direction=bible_to_ub). One query surfaces both Bible matches and the relevant UB content. Optional fil...
Risk signalsAccepts freeform code/query input (query)
Part of the Urantia Papers server.
Free to start. No card required.
AI agents use bible.search.semantic to create or modify resources in Urantia Papers. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call bible.search.semantic repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Urantia Papers.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"bible.search.semantic": {
"limits": [
{
"counter": "bible.search.semantic_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Urantia Papers policy for all 19 tools.
These attack patterns abuse exactly the kind of access bible.search.semantic gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Free-form natural-language search across all Bible chunks, ranked by cosine similarity. Each result includes the top-N pre-computed Urantia paragraphs related to that chunk via bible_parallels (direction=bible_to_ub). One query surfaces both Bible matches and the relevant UB content. Optional filters: canon (ot, deuterocanon, nt) and book_code. Set urantia_parallel_limit to 0 to suppress the UB attachment. Requires OPENAI_API_KEY.. It is categorised as a Write tool in the Urantia Papers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Urantia Papers MCP server in PolicyLayer and add a rule for bible.search.semantic: 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 Urantia Papers. Nothing to install.
bible.search.semantic is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bible.search.semantic 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.search.semantic. 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.search.semantic is provided by the Urantia Papers MCP server (https://api.urantia.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Urantia Papers tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.