updateResourcePermission
Update the access level on an existing permission row. Override flags are NOT touched — use setResourcePermissionOverride for those. Refuses self-escalation. Rate limit 30/min.
This record as markdown: /tools/io-stablebaseline-sb/updateresourcepermission.md
What updateResourcePermission does on Stable Baseline
AI agents use updateResourcePermission to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
level | string | Yes | |
permission_id | string | Yes | UUID of the resource_permissions row |
Parameters from the server's own tool schema.
Why updateResourcePermission is rated Medium
This tool modifies access control settings reversibly (access levels can be changed again), making it a Write operation rather than Destructive. However, the blast radius is high because misconfigured permissions could grant unintended access to sensitive company resources (docs, diagrams, plans, Knowledge Graph).
From the tool's definition Tool name 'updateResourcePermission' and description states it 'Update[s] the access level on an existing permission row' — a modification of access control data.
Attacks that exploit this kind of access
The rule that runs updateResourcePermission safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For updateResourcePermission, this is the rule to start with:
updateResourcePermission 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 Stable Baseline, apply this rule, and every updateResourcePermission call is checked against it from then on.
Questions about updateResourcePermission
Update the access level on an existing permission row. Override flags are NOT touched — use setResourcePermissionOverride for those. Refuses self-escalation. Rate limit 30/min. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
updateResourcePermission accepts 2 parameters: level, permission_id. Required: level, permission_id. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for updateResourcePermission: 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 Stable Baseline. Nothing to install.
updateResourcePermission 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 updateResourcePermission 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 updateResourcePermission. 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.
updateResourcePermission is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue