adaptercloud_rbac_check
Check whether an actor has permission for an action on a resource.
This record as markdown: /tools/burdenoff-adaptercloud-mcp/adaptercloud-rbac-check.md
What adaptercloud_rbac_check does on Adaptercloud
AI agents call adaptercloud_rbac_check to retrieve information from Adaptercloud 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 |
|---|---|---|---|
layer | string | — | workspace or global (default: workspace) |
action | string | Yes | Action like read/write/delete |
actorId | string | Yes | Actor id (user/app/service/super_admin) |
scopeId | string | — | Scope id (workspaceId or tenantId) |
actorType | string | — | Actor type (default: USER) |
resourceId | string | — | Specific resource id (optional) |
resourceType | string | Yes | Resource type like project/task |
Parameters from the server's own tool schema.
Why adaptercloud_rbac_check is rated Low
Even though adaptercloud_rbac_check only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs adaptercloud_rbac_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adaptercloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adaptercloud_rbac_check, this is the rule to start with:
adaptercloud_rbac_check 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 Adaptercloud, apply this rule, and every adaptercloud_rbac_check call is checked against it from then on.
Questions about adaptercloud_rbac_check
Check whether an actor has permission for an action on a resource. It is categorised as a Read tool in the Adaptercloud MCP Server, which means it retrieves data without modifying state.
adaptercloud_rbac_check accepts 7 parameters: layer, action, actorId, scopeId, actorType, resourceId, resourceType. Required: action, actorId, resourceType. The full parameter table on this page comes from the server's own tool schema.
Register the Adaptercloud MCP server in PolicyLayer and add a rule for adaptercloud_rbac_check: 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 Adaptercloud. Nothing to install.
adaptercloud_rbac_check 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 adaptercloud_rbac_check 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 adaptercloud_rbac_check. 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.
adaptercloud_rbac_check is provided by the Adaptercloud MCP server (@burdenoff/adaptercloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adaptercloud, and thousands of servers like it.
This server
Across the catalogue