resources_search
AI agents call resources_search to retrieve information from CyPerf MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations typically retrieve or query data without side effects. While the empty description introduces some uncertainty, the tool name follows Read-category patterns (search, list, query). The sibling tools show a mix of Read (agents_get, agents_list), Write (agents_export_files), and Destructive (agents_delete) operations, consistent with this being a management platform where 'search' is exploratory.
From the tool's definition Tool name 'resources_search' indicates a search/query operation. The description is empty, limiting direct evidence, but naming conventions and context within a network testing platform suggest data retrieval rather than modification or execution.
Attacks that exploit this kind of access
resources_search. It is categorised as a Read tool in the CyPerf MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CyPerf MCP Server MCP server in PolicyLayer and add a rule for resources_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 CyPerf MCP Server. Nothing to install.
resources_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 resources_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 resources_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.
resources_search is provided by the CyPerf MCP Server MCP server (keysight/cyperf-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 →