list_secret_scanning_alerts

List the current GitHub Advanced Security secret scanning alerts for a repository

Server GHAS MCP server (GitHub Advanced Security) rajbos/ghas-mcp-server
Category Read
Risk class Low
Parameters 00 required

What list_secret_scanning_alerts does on GHAS MCP server (GitHub Advanced Security)

AI agents call list_secret_scanning_alerts to retrieve information from GHAS MCP server (GitHub Advanced Security) 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 and queries existing security alert data from GitHub Advanced Security without creating, modifying, deleting, or executing any operations. It is a read-only data retrieval function with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name contains 'list' and description states 'List the current GitHub Advanced Security secret scanning alerts' - a pure retrieval operation with no mutation or side effects.

Questions about list_secret_scanning_alerts

What does the list_secret_scanning_alerts tool do? +

List the current GitHub Advanced Security secret scanning alerts for a repository. It is categorised as a Read tool in the GHAS MCP server (GitHub Advanced Security) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_secret_scanning_alerts? +

Register the GHAS MCP server (GitHub Advanced Security) 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 GHAS MCP server (GitHub Advanced Security). 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 GHAS MCP server (GitHub Advanced Security) MCP server (rajbos/ghas-mcp-server). 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.