search_scripture
AI agents call search_scripture 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.
The tool performs a search operation on biblical scripture data. Despite having an empty description, the name and context of sibling tools (all retrieval/query functions) strongly suggest this retrieves or queries scriptural information with no side effects. The server explicitly provides 'full-text biblical searches' and 'topical studies' as core features.
From the tool's definition Tool name 'search_scripture' indicates a search operation, consistent with sibling tools like 'get_verse', 'get_cross_references', and 'search_by_topic' which are all Read operations that retrieve biblical data without modification.
Attacks that exploit this kind of access
search_scripture. 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 search_scripture: 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.
search_scripture 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_scripture 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_scripture. 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_scripture 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 →