AI agents call search_components to retrieve information from MCP Modus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation against documentation to retrieve matching components. It retrieves information without creating, modifying, deleting, or executing any code. The operation is purely informational with no blast radius if misused by an AI agent—worst case it returns irrelevant search results.
From the tool's definition Tool description states it 'Search for Modus Web Components by name or keyword. Returns a list of matching components with brief descriptions.' The verb 'search' and 'returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Search for Modus Web Components by name or keyword. Returns a list of matching components with brief descriptions. It is categorised as a Read tool in the MCP Modus MCP Server, which means it retrieves data without modifying state.
Register the MCP Modus MCP server in PolicyLayer and add a rule for search_components: 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 Modus. Nothing to install.
search_components 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_components 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_components. 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_components is provided by the MCP Modus MCP server (julianoczkowski/mcp-modus). 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 →