mcp_discover
Search 1000+ MCP servers by capability (300 sats/call; free tier 100 calls/mo)
This record as markdown: /tools/com-thetempleofdoom-hyperion-hyperion/mcp-discover.md
What mcp_discover does on Hyperion
AI agents call mcp_discover to retrieve information from Hyperion without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results to return (default 10, max 50). |
query | string | Yes | Free-text query describing the capability you need (e.g. "payments", "browser automation", "sql database", "image generation"). |
Parameters from the server's own tool schema.
Why mcp_discover is rated Low
Even though mcp_discover only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs mcp_discover safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hyperion, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_discover, this is the rule to start with:
mcp_discover is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hyperion, apply this rule, and every mcp_discover call is checked against it from then on.
Questions about mcp_discover
Search 1000+ MCP servers by capability (300 sats/call; free tier 100 calls/mo). It is categorised as a Read tool in the Hyperion MCP Server, which means it retrieves data without modifying state.
mcp_discover accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Hyperion MCP server in PolicyLayer and add a rule for mcp_discover: 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 Hyperion. Nothing to install.
mcp_discover 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 mcp_discover 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 mcp_discover. 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.
mcp_discover is provided by the Hyperion MCP server (https://hyperion.thetempleofdoom.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hyperion, and thousands of servers like it.
This server
Across the catalogue