deleteResourcePermission
Delete a resource_permissions row. Refuses if the row is the LAST admin grant on the resource. Rate limit 30/min. Use when the user asks to revoke access, remove access, take away access, unshare, or delete a permission grant on a specific resource.
This record as markdown: /tools/io-stablebaseline-sb/deleteresourcepermission.md
What deleteResourcePermission does on Stable Baseline
AI agents call deleteResourcePermission to permanently remove resources in Stable Baseline, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
permission_id | string | Yes | UUID of the resource_permissions row to delete |
Parameters from the server's own tool schema.
Why deleteResourcePermission is rated Critical
This tool performs an irreversible deletion of permission records. While it includes a safeguard (refusing if the row is the last admin grant), the core function is to permanently remove access control entries. Misuse by an AI agent could result in authorized users losing access to critical company resources (docs, diagrams, plans, knowledge graph).
From the tool's definition Tool name contains 'delete'; description explicitly states 'Delete a resource_permissions row' and is used when 'revoke access, remove access, take away access, unshare, or delete a permission grant'.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs deleteResourcePermission 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 deleteResourcePermission, this is the rule to start with:
deleteResourcePermission is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every deleteResourcePermission call is checked against it from then on.
Questions about deleteResourcePermission
Delete a resource_permissions row. Refuses if the row is the LAST admin grant on the resource. Rate limit 30/min. Use when the user asks to revoke access, remove access, take away access, unshare, or delete a permission grant on a specific resource. It is categorised as a Destructive tool in the Stable Baseline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteResourcePermission accepts 1 parameter: permission_id. Required: 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 deleteResourcePermission: 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.
deleteResourcePermission is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteResourcePermission 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 deleteResourcePermission. 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.
deleteResourcePermission 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.
Across the catalogue