discover-tools
List and load additional ${serverName} tools that aren
This record as markdown: /tools/io-github-dave-london-build/discover-tools.md
What discover-tools does on Build
AI agents call discover-tools to retrieve information from Build without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why discover-tools is rated Low
This tool retrieves metadata about available tools on the server. It performs a listing/discovery operation without creating, modifying, deleting, or executing external code. The truncated description appears incomplete ('that aren') but the 'discover' and 'list' verbs indicate a read-only information retrieval function.
From the tool's definition Tool name is 'discover-tools' and description indicates it 'List and load additional tools' - a discovery/enumeration operation with no data modification
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 Build, 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 Build, apply this rule, and every discover-tools call is checked against it from then on.
Questions about discover-tools
List and load additional ${serverName} tools that aren. It is categorised as a Read tool in the Build MCP Server, which means it retrieves data without modifying state.
Register the Build 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 Build. 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 Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Build, and thousands of servers like it.
This server
Across the catalogue