AI agents call search to retrieve information from Unfragile without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries an existing knowledge graph and returns search results. It retrieves information without creating, modifying, deleting, or executing arbitrary code. The data-feeding aspect is passive telemetry collection, not a reversible write operation that an end-user controls. Misuse (e.g., searching for sensitive tool names) poses minimal blast radius compared to tools that modify or execute.
From the tool's definition Tool description states it 'Search[es]' and 'Returns ranked results' — a retrieval operation with no side effects. The phrase 'Every query feeds the graph' indicates telemetry/logging but does not alter the user's data or external systems.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Search the Unfragile match graph for AI tools, frameworks, APIs, MCP servers, agents, and more. Returns ranked results with capability matches and graph signals. Every query feeds the graph. It is categorised as a Read tool in the Unfragile MCP Server, which means it retrieves data without modifying state.
Register the Unfragile MCP server in PolicyLayer and add a rule for search: 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 Unfragile. Nothing to install.
search 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 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. 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 is provided by the Unfragile MCP server (savirinc/unfragile-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 →