update_permission_set
Update an existing Sanka permission set for workspace governance.
This record as markdown: /tools/sankahq-sanka-mcp/update-permission-set.md
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 update_permission_set is rated Medium
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
The rule that runs update_permission_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_permission_set, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every update_permission_set call is checked against it from then on.
Questions about update_permission_set
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.
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.
update_permission_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue