AI agents call get_entity_relations 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.
This tool retrieves relationships between biblical entities without modifying, deleting, or executing external operations. The empty description is a minor confidence reducer, but the naming pattern and server's read-only design strongly indicate a data retrieval function. Confidence is not higher because the description is uninformative, but the contextual evidence from sibling tools and server purpose is clear.
From the tool's definition Tool name 'get_entity_relations' and server context indicate retrieval of relational data about biblical entities (people, places, events).
Attacks that exploit this kind of access
get_entity_relations. 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 get_entity_relations: 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.
get_entity_relations 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 get_entity_relations 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 get_entity_relations. 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.
get_entity_relations 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 →