create_credentials_api3 · Looker MCP Server MCP

WHAT IT DOES

What create_credentials_api3 does on Looker MCP Server

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

Creating API credentials is a reversible write operation that generates new authentication tokens or keys. However, this carries high severity because compromised API credentials can grant attackers persistent access to the Looker instance and its data.

From the tool's definition Tool name 'create_credentials_api3' indicates creation of API credentials; sibling tools on server include user management and content creation functions, confirming this server manages sensitive Looker resources and authentication materials.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_credentials_api3 Rate-limited

create_credentials_api3 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": {
    "create_credentials_api3": {
      "limits": [
        {
          "counter": "create_credentials_api3_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 create_credentials_api3

What does the create_credentials_api3 tool do? +

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

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

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

Can I rate-limit create_credentials_api3? +

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

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

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