update_schedule · Looker MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_schedule does on Looker MCP Server

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

WHY IT NEEDS A POLICY

Why update_schedule needs a policy

The tool name suggests it updates (modifies) a schedule, which is a reversible Write operation. However, the empty description prevents confirmation of scope—it could affect dashboard refresh schedules, data refresh timing, or alert configurations. Without clarity on what 'schedule' refers to or what parameters it accepts, confidence is low.

From the tool's definition Tool name 'update_schedule' indicates modification of an existing schedule; no description provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_schedule Rate-limited

update_schedule 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": {
    "update_schedule": {
      "limits": [
        {
          "counter": "update_schedule_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 Looker MCP Server, so you can run agents against it safely.

FAQ

Questions about update_schedule

What does the update_schedule tool do? +

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

How do I enforce a policy on update_schedule? +

Register the Looker MCP Server MCP server in PolicyLayer and add a rule for update_schedule: 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 update_schedule? +

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

Can I rate-limit update_schedule? +

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

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

update_schedule 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.