trigger_project_ci_run · Looker MCP Server MCP

WHAT IT DOES

What trigger_project_ci_run does on Looker MCP Server

AI agents invoke trigger_project_ci_run to trigger actions in Looker MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why trigger_project_ci_run needs a policy

This tool triggers automated CI/CD operations, which execute code and external systems. While the description is empty, the function name and context within a Looker administration server with LookML editing capabilities strongly indicate this runs project builds/deployments.

From the tool's definition Tool name 'trigger_project_ci_run' indicates execution of CI/CD pipeline operations. The server description confirms the MCP provides capabilities for 'administering' Looker and 'editing LookML,' and sibling tools include project administration functions…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_project_ci_run Rate-limited

trigger_project_ci_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "trigger_project_ci_run": {
      "limits": [
        {
          "counter": "trigger_project_ci_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about trigger_project_ci_run

What does the trigger_project_ci_run tool do? +

trigger_project_ci_run. It is categorised as a Execute tool in the Looker MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trigger_project_ci_run? +

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

What risk level is trigger_project_ci_run? +

trigger_project_ci_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit trigger_project_ci_run? +

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

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

trigger_project_ci_run is provided by the Looker MCP Server MCP server (ultrathink-solutions/looker-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.