disable_stale_sessions · Looker MCP Server MCP

WHAT IT DOES

What disable_stale_sessions does on Looker MCP Server

AI agents use disable_stale_sessions 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 disable_stale_sessions needs a policy

An AI agent can call disable_stale_sessions faster than any human can review — one bad instruction and it creates or modifies resources in Looker MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_stale_sessions Rate-limited

disable_stale_sessions 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": {
    "disable_stale_sessions": {
      "limits": [
        {
          "counter": "disable_stale_sessions_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 disable_stale_sessions

What does the disable_stale_sessions tool do? +

disable_stale_sessions. 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 disable_stale_sessions? +

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

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

Can I rate-limit disable_stale_sessions? +

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

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

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