gcp_run_list_services
List all Cloud Run services
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-run-list-services.md
What gcp_run_list_services does on GCP MCP Server
AI agents call gcp_run_list_services 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.
Why gcp_run_list_services is rated Low
The tool retrieves a list of Cloud Run services without creating, modifying, or deleting any resources. Read-only enumeration of services poses minimal risk; the only concern is minor information disclosure about infrastructure topology.
From the tool's definition 'List all Cloud Run services' — listing is a read-only operation with no side effects
Attacks that exploit this kind of access
The rule that runs gcp_run_list_services 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_run_list_services, this is the rule to start with:
gcp_run_list_services is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GCP MCP Server, apply this rule, and every gcp_run_list_services call is checked against it from then on.
Questions about gcp_run_list_services
List all Cloud Run services. It is categorised as a Read tool in the GCP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_run_list_services: 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.
gcp_run_list_services is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gcp_run_list_services 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.
Set action: deny in the PolicyLayer policy for gcp_run_list_services. 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.
gcp_run_list_services 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.
More on GCP MCP Server, and thousands of servers like it.
This server
Across the catalogue