get_cross_references
AI agents call get_cross_references to retrieve information from SolaGuard MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or looks up cross-references within biblical texts—a query operation with no side effects. It fits the 'Read' category as it provides data retrieval functionality aligned with the server's stated purpose of 'scripture lookup' and 'cross-referencing.' The empty description slightly reduces confidence, but the naming pattern and context of similar read-only tools strongly suggest lookup/retrieval…
From the tool's definition Tool name 'get_cross_references' indicates retrieval of existing cross-reference data; no description provided but consistent with sibling tools (get_book_info, get_verse, get_verse_context, search_scripture) which are all read operations that query biblical…
Attacks that exploit this kind of access
get_cross_references. It is categorised as a Read tool in the SolaGuard MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SolaGuard MCP Server MCP server in PolicyLayer and add a rule for get_cross_references: 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 SolaGuard MCP Server. Nothing to install.
get_cross_references 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_cross_references 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_cross_references. 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_cross_references is provided by the SolaGuard MCP Server MCP server (jissac/solaguard-mcp-server). 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 →