secret-list

Lists repository, organization, or environment secret names and metadata. Secret values are not exposed by GitHub.

SERVERHttp SOURCE@paretools/http

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-http/secret-list.md

WHAT IT DOES

What secret-list does on Http

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

RISK

Why secret-list is rated Low

This tool retrieves metadata about secrets without exposing their actual values. It has no side effects—it only queries and lists information. The blast radius is minimal since the sensitive data (secret values) are explicitly excluded from the output. Classification as Read is appropriate.

From the tool's definition Tool 'secret-list' 'Lists repository, organization, or environment secret names and metadata. Secret values are not exposed by GitHub.' The description explicitly states only names and metadata are returned, not actual secret values.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs secret-list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Http, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For secret-list, this is the rule to start with:

secret-list Allowed

secret-list 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": {
    "secret-list": {}
  }
}

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

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

FAQ

Questions about secret-list

What does the secret-list tool do? +

Lists repository, organization, or environment secret names and metadata. Secret values are not exposed by GitHub. It is categorised as a Read tool in the Http MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on secret-list? +

Register the Http MCP server in PolicyLayer and add a rule for secret-list: 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 Http. Nothing to install.

What risk level is secret-list? +

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

Can I rate-limit secret-list? +

Yes. Add a rate_limit block to the secret-list 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 secret-list completely? +

Set action: deny in the PolicyLayer policy for secret-list. 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 secret-list? +

secret-list is provided by the Http MCP server (@paretools/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Http, and thousands of servers like it.

This server

All 202 Http tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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