Search MAGMA documentation using advanced multi-query and hybrid search
AI agents call search_magma to retrieve information from MCP MAGMA Handbook Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs semantic search and information retrieval from documentation. It queries existing data without side effects, modifying, creating, deleting, or executing operations. The worst-case misuse scenario would be an AI agent retrieving sensitive or inappropriate documentation, which is a low-severity information disclosure. No financial, destructive, or code execution risks are present.
From the tool's definition The tool is described as "Search MAGMA documentation using advanced multi-query and hybrid search", which is a retrieval operation with no modification, creation, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search MAGMA documentation using advanced multi-query and hybrid search. It is categorised as a Read tool in the MCP MAGMA Handbook Server MCP Server, which means it retrieves data without modifying state.
Register the MCP MAGMA Handbook Server MCP server in PolicyLayer and add a rule for search_magma: 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 MCP MAGMA Handbook Server. Nothing to install.
search_magma 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_magma 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_magma. 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_magma is provided by the MCP MAGMA Handbook Server MCP server (legenai/mcp-magma-handbook). 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 →