list_secret_scanning_alerts

List secret-scanning alerts for a repo, or for an org if repo is omitted.

Server Ghe Mcp Gateway mholzinger/ghe-mcp-gateway
Category Read
Risk class Low
Parameters 00 required

What list_secret_scanning_alerts does on Ghe Mcp Gateway

AI agents call list_secret_scanning_alerts to retrieve information from Ghe Mcp Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_secret_scanning_alerts needs a policy

This tool retrieves (reads) security alert data about detected secrets in repositories or organizations. While it performs no write, execute, or destructive operations, the severity is high because it exposes sensitive information about discovered secrets and potential security vulnerabilities, which could be exploited if an AI agent misuses the alerts data or leaks it.

From the tool's definition Tool is named 'list_secret_scanning_alerts' and description states it 'List[s] secret-scanning alerts' — a retrieval operation with no modification of data. The verb 'list' and context of 'read-only safety by default' confirm this is a query/retrieval action.

Questions about list_secret_scanning_alerts

What does the list_secret_scanning_alerts tool do? +

List secret-scanning alerts for a repo, or for an org if repo is omitted. It is categorised as a Read tool in the Ghe Mcp Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_secret_scanning_alerts? +

Register the Ghe Mcp Gateway MCP server in PolicyLayer and add a rule for list_secret_scanning_alerts: 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 Ghe Mcp Gateway. Nothing to install.

What risk level is list_secret_scanning_alerts? +

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

Can I rate-limit list_secret_scanning_alerts? +

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

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

list_secret_scanning_alerts is provided by the Ghe Mcp Gateway MCP server (mholzinger/ghe-mcp-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.