update_permission_set · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_permission_set does on Sanka MCP Server

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

WHY IT NEEDS A POLICY

Why update_permission_set needs a policy

This tool modifies permission configurations that control who can access what resources in a workspace. While reversible (Write rather than Destructive), misuse could grant an AI agent excessive permissions, escalate privileges, or compromise workspace security. High severity due to the security-sensitive nature of permission management and potential blast radius across the workspace.

From the tool's definition Tool name 'update_permission_set' combined with description 'Update an existing Sanka permission set for workspace governance' indicates modification of access control settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_permission_set Rate-limited

update_permission_set 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_permission_set": {
      "limits": [
        {
          "counter": "update_permission_set_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 Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about update_permission_set

What does the update_permission_set tool do? +

Update an existing Sanka permission set for workspace governance. It is categorised as a Write tool in the Sanka 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_permission_set? +

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

What risk level is update_permission_set? +

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

Can I rate-limit update_permission_set? +

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

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

update_permission_set is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.