logging_create_log_sink · Google Cloud MCP: Risk & Policy

WHAT IT DOES

What logging_create_log_sink does on Google Cloud

AI agents use logging_create_log_sink to create or update resources in Google Cloud — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Cloud environment.

WHY IT NEEDS A POLICY

Why logging_create_log_sink needs a policy

Creating a log sink modifies the logging infrastructure by establishing new rules for where logs are sent. This is a reversible Write operation—sinks can be updated or deleted. However, it has high severity because a misconfigured sink could redirect sensitive logs to unauthorized destinations, exfiltrate data, or disrupt logging pipelines.

From the tool's definition Tool name 'logging_create_log_sink' indicates creation of a log sink resource in Cloud Logging. The verb 'create' and 'sink' (a routing destination for logs) suggest data flow modification and resource creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

logging_create_log_sink Rate-limited

logging_create_log_sink stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "logging_create_log_sink": {
      "limits": [
        {
          "counter": "logging_create_log_sink_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Cloud, so you can run agents against it safely.

FAQ

Questions about logging_create_log_sink

What does the logging_create_log_sink tool do? +

logging_create_log_sink. It is categorised as a Write tool in the Google Cloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on logging_create_log_sink? +

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

What risk level is logging_create_log_sink? +

logging_create_log_sink is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit logging_create_log_sink? +

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

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

logging_create_log_sink is provided by the Google Cloud MCP server (lockon-n/google-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.