discover_tools
Meta-tool: navigate DC Hub's 60+ tools by FAMILY instead of scanning the whole list. Returns _entity=tool_families — each family has a when-to-use note + its flagship tools (facility, market, grid_power, gas_btm, site_geometry, fiber, deals_news, account_meta), optionally filtered by a query. Cal...
This record as markdown: /tools/cloud-dchub-mcp-server/discover-tools.md
What discover_tools does on Mcp Server
AI agents call discover_tools to retrieve information from Mcp Server 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 |
|---|---|---|---|
query | string | — | Optional keyword to filter families/tools, e.g. "site selection", "grid queue", "fiber", "deals", "market" |
Parameters from the server's own tool schema.
Why discover_tools is rated Low
discover_tools is a read-only navigation/discovery utility that retrieves and filters metadata about the MCP server's tool families and their schemas. It has no side effects, cannot modify state, and serves purely to help users find appropriate tools. This is equivalent to a help or list command, placing it firmly in the Read category with low severity since misuse cannot cause material harm.
From the tool's definition Tool returns structured metadata about available tools via query filtering (navigate, list, returns _entity=tool_families). No data creation, modification, deletion, or execution of external operations.
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 Mcp Server, 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 Mcp Server, apply this rule, and every discover_tools call is checked against it from then on.
Questions about discover_tools
Meta-tool: navigate DC Hub's 60+ tools by FAMILY instead of scanning the whole list. Returns _entity=tool_families — each family has a when-to-use note + its flagship tools (facility, market, grid_power, gas_btm, site_geometry, fiber, deals_news, account_meta), optionally filtered by a query. Call this FIRST when you are unsure which tool fits a task; then call the chosen tool (its full schema is in tools/list). This is a navigation layer, not the exhaustive catalog — tools/list stays canonical. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
discover_tools accepts 1 parameter: query. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server 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 Mcp Server. 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 Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue