Full-text search the mirrored docs.electra.one documentation.
AI agents call search_docs to retrieve information from Electra One without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves information from static documentation without side effects. It is a pure read operation with minimal blast radius—the worst case being that an AI agent performs unexpected searches, which has no operational impact on the Electra One device or system state.
From the tool's definition Tool performs 'full-text search' on documentation with no modification or execution capabilities. The description explicitly indicates it 'search[es]' (retrieves information) rather than modifying, executing, or deleting.
Attacks that exploit this kind of access
Full-text search the mirrored docs.electra.one documentation. It is categorised as a Read tool in the Electra One MCP Server, which means it retrieves data without modifying state.
Register the Electra One MCP server in PolicyLayer and add a rule for search_docs: 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 Electra One. Nothing to install.
search_docs 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_docs 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_docs. 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_docs is provided by the Electra One MCP server (roomi-fields/electra-one-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 →