discover_tools
Find the right tool WITHOUT loading all 160+ schemas into your context. Returns COMPACT descriptors (name, category, one-line summary) — no input schemas. Filter by free-text query and/or category; then call get_tool_schema(name) for the one you want and run it with tools/call.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/discover-tools.md
What discover_tools does on Gateway
AI agents call discover_tools to retrieve information from Gateway 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 | integer | — | max results (default 40, max 150) |
query | string | — | free-text match over tool name/summary |
category | string | — | filter to one category, e.g. finance, trades, memory, browser, vault, web, meta |
Parameters from the server's own tool schema.
Why discover_tools is rated Low
This tool only retrieves and returns descriptive metadata about available tools. It performs a read/search operation with no side effects, no data modification, and no execution of external operations. The blast radius of misuse is minimal as it only surfaces tool listings.
From the tool's definition Find the right tool WITHOUT loading all 160+ schemas into your context. Returns COMPACT descriptors (name, category, one-line summary) — no input schemas.
Attacks that exploit this kind of access
The rule that runs discover_tools safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For discover_tools, this is the rule to start with:
discover_tools 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 Gateway, apply this rule, and every discover_tools call is checked against it from then on.
Questions about discover_tools
Find the right tool WITHOUT loading all 160+ schemas into your context. Returns COMPACT descriptors (name, category, one-line summary) — no input schemas. Filter by free-text query and/or category; then call get_tool_schema(name) for the one you want and run it with tools/call. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
discover_tools accepts 3 parameters: limit, query, category. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for discover_tools: 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 Gateway. Nothing to install.
discover_tools 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 discover_tools 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 discover_tools. 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.
discover_tools is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue