Search agents by keywords in name, description, or content
AI agents call search_agents to retrieve information from Pantheon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data (searching agent instructions by keywords) with no side effects, no code execution, and no data modification. It fits the Read category as a search/query operation. Severity is low because misuse would only expose existing agent instructions already on the server, with no ability to modify, delete, or execute operations.
From the tool's definition Tool description states 'Search agents by keywords' - a query/search operation with no modification or execution of external systems. The action is purely informational retrieval.
Documented attack patterns abuse exactly the kind of access search_agents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pantheon, and nothing reaches the server without passing your rules. This is the rule we recommend for search_agents:
{
"version": "1",
"default": "deny",
"tools": {
"search_agents": {}
}
}search_agents is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search agents by keywords in name, description, or content. It is categorised as a Read tool in the Pantheon MCP Server, which means it retrieves data without modifying state.
Register the Pantheon MCP server in PolicyLayer and add a rule for search_agents: 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 Pantheon. Nothing to install.
search_agents 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_agents 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_agents. 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_agents is provided by the Pantheon MCP server (valado/pantheon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pantheon, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Pantheon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.