listResourcePermissions
List explicit permission grants on a resource (workspace/project/folder/document/improvement/plan), including principal type (user|team), level (none|read|write|admin), and 3-state overrides for documents/improvements/plans. Read-only. Use when the user asks 'who can see this', 'who has access', ...
This record as markdown: /tools/io-stablebaseline-sb/listresourcepermissions.md
What listResourcePermissions does on Stable Baseline
AI agents call listResourcePermissions to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
resource_id | string | Yes | UUID of the resource |
resource_type | string | Yes |
Parameters from the server's own tool schema.
Why listResourcePermissions is rated Low
This tool retrieves and queries access control metadata on resources without modifying, creating, or deleting data. It is purely informational—listing who has what permissions. The 'read-only' designation and absence of any action verbs beyond 'list' confirm it belongs in the Read category.
From the tool's definition Tool name 'listResourcePermissions' and description explicitly states 'Read-only' and 'List explicit permission grants'. Returns permission metadata without modification or side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs listResourcePermissions 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 listResourcePermissions, this is the rule to start with:
listResourcePermissions is read-only, so it stays allowed. 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 listResourcePermissions call is checked against it from then on.
Questions about listResourcePermissions
List explicit permission grants on a resource (workspace/project/folder/document/improvement/plan), including principal type (user|team), level (none|read|write|admin), and 3-state overrides for documents/improvements/plans. Read-only. Use when the user asks 'who can see this', 'who has access', 'what permissions are set on this', or to audit existing access on a resource. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listResourcePermissions accepts 2 parameters: resource_id, resource_type. Required: resource_id, resource_type. 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 listResourcePermissions: 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.
listResourcePermissions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listResourcePermissions 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 listResourcePermissions. 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.
listResourcePermissions 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