AI agents call route_entity_query to retrieve information from Bible MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to route queries about biblical entities within a read-only knowledge base system. Despite the empty description, the consistent pattern of sibling tools that retrieve and search biblical data, combined with the server's documented read-only nature (semantic search, retrieval, exploration), strongly indicates this tool retrieves or queries data without side effects.
From the tool's definition Tool name 'route_entity_query' combined with sibling tools that are all Read operations (search_bible, search_entities, lookup_passage, get_entity_passages, get_entity_relations, expand_context, suggest_related_passages, summarize_passage).
Attacks that exploit this kind of access
route_entity_query. It is categorised as a Read tool in the Bible MCP MCP Server, which means it retrieves data without modifying state.
Register the Bible MCP server in PolicyLayer and add a rule for route_entity_query: 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 MCP. Nothing to install.
route_entity_query 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 route_entity_query 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 route_entity_query. 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.
route_entity_query is provided by the Bible MCP server (parsifal295/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 →