discover-tools

List and load additional ${serverName} tools that aren

SERVERGithub SOURCE@paretools/github

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-github/discover-tools.md

WHAT IT DOES

What discover-tools does on Github

AI agents call discover-tools to retrieve information from Github without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why discover-tools is rated Low

This tool lists and loads available tools from the MCP server, which is a read operation that queries what capabilities exist. While it involves loading tool metadata, it does not execute, modify, create, or delete data—it simply enumerates existing tools. The incomplete description ("that aren") is a minor flaw, but the core function is clearly informational.

From the tool's definition discover-tools" description states "List and load additional ${serverName} tools" — primarily a listing/discovery operation that retrieves available tool information.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs discover-tools safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Github, 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 Allowed

discover-tools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "discover-tools": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every discover-tools call is checked against it from then on.

FAQ

Questions about discover-tools

What does the discover-tools tool do? +

List and load additional ${serverName} tools that aren. It is categorised as a Read tool in the Github MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on discover-tools? +

Register the Github 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 Github. Nothing to install.

What risk level is discover-tools? +

discover-tools is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit discover-tools? +

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.

How do I block discover-tools completely? +

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.

What MCP server provides discover-tools? +

discover-tools is provided by the Github MCP server (@paretools/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Github, and thousands of servers like it.

This server

All 202 Github tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →