AI agents call search_entities 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 to search for biblical entities (people, places, events) without modifying data. The server is explicitly described as enabling 'search and retrieval' with no write, delete, or execution capabilities mentioned. Sibling tools confirm a read-only retrieval pattern. No side effects or data modifications are evident.
From the tool's definition Tool name 'search_entities' combined with server context indicating 'semantic search and retrieval' and sibling tools like 'search_bible', 'get_entity_passages', 'lookup_passage' that retrieve biblical data.
Attacks that exploit this kind of access
search_entities. 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 search_entities: 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.
search_entities 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 search_entities 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 search_entities. 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.
search_entities 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 →