gcp_secrets_list

List all secrets in the project

SERVERGCP MCP Server SOURCEahmedselimmansor-ctrl/gcp_mcp_server

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/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-secrets-list.md

WHAT IT DOES

What gcp_secrets_list does on GCP MCP Server

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

RISK

Why gcp_secrets_list is rated Low

This tool retrieves secrets metadata without creating, modifying, or deleting any data. However, secrets typically contain sensitive credentials (API keys, passwords, tokens), so unauthorized enumeration could expose sensitive information at scale. Severity is high due to the sensitive nature of secrets, but category remains Read because the operation itself is non-destructive and read-only.

From the tool's definition Tool name 'gcp_secrets_list' and description 'List all secrets in the project' indicate a retrieval operation with no modification. The verb 'list' is a classic read operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gcp_secrets_list safely

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

gcp_secrets_list Allowed

gcp_secrets_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": {
    "gcp_secrets_list": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect GCP MCP Server, apply this rule, and every gcp_secrets_list call is checked against it from then on.

FAQ

Questions about gcp_secrets_list

What does the gcp_secrets_list tool do? +

List all secrets in the project. It is categorised as a Read tool in the GCP MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gcp_secrets_list? +

Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_secrets_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 GCP MCP Server. Nothing to install.

What risk level is gcp_secrets_list? +

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

Can I rate-limit gcp_secrets_list? +

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

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

gcp_secrets_list is provided by the GCP MCP Server MCP server (ahmedselimmansor-ctrl/gcp_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GCP MCP Server, and thousands of servers like it.

This server

All 295 GCP MCP Server 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 →