update_resource_permissions

SERVERDoit SOURCE@doitintl/doit-mcp-server

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/update-resource-permissions.md

WHAT IT DOES

What update_resource_permissions does on Doit

AI agents use update_resource_permissions to create or update resources in Doit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doit environment.

Parameter	Type	Required	Description
`public`	object	—	Public visibility: editor or viewer shares with all users in the organization. For reports, alerts and budgets, omission or null makes the resource private; omi
`resourceId`	string	Yes	The ID of the resource (alert, budget, report, or allocation) to update permissions for.
`permissions`	array	Yes	Required nonempty replacement list, not a merge. Include every permission to retain and exactly one owner.
`resourceType`	string	Yes	The type of resource to update sharing settings for. One of: alerts, budgets, reports, allocations.

Parameters from the server's own tool schema.

RISK

Why update_resource_permissions is rated Medium

An AI agent can call update_resource_permissions faster than any human can review: one bad instruction and it creates or modifies resources in Doit by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_resource_permissions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_resource_permissions, this is the rule to start with:

update_resource_permissions Rate-limited

update_resource_permissions 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_resource_permissions": {
      "limits": [
        {
          "counter": "update_resource_permissions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every update_resource_permissions call is checked against it from then on.

FAQ

Questions about update_resource_permissions

What does the update_resource_permissions tool do? +

Use this when the user wants to change who a Cloud Analytics resource is shared with or update access levels. Replaces sharing settings with PUT for a specific alert, budget, custom report, or allocation. Requires resourceType, resourceId and a nonempty permissions list with exactly one owner. Read current permissions first and retain all intended entries. Only the current owner or a user with Ownership assignment permission may transfer ownership. Omitted public makes reports, alerts and budgets private; allocations reject omitted/null public. Do NOT use this to view current permissions (use get_resource_permissions). It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_resource_permissions accept? +

update_resource_permissions accepts 4 parameters: public, resourceId, permissions, resourceType. Required: resourceId, permissions, resourceType. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_resource_permissions? +

Register the Doit MCP server in PolicyLayer and add a rule for update_resource_permissions: 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 Doit. Nothing to install.

What risk level is update_resource_permissions? +

update_resource_permissions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_resource_permissions? +

Yes. Add a rate_limit block to the update_resource_permissions 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.

How do I block update_resource_permissions completely? +

Set action: deny in the PolicyLayer policy for update_resource_permissions. 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.

What MCP server provides update_resource_permissions? +

update_resource_permissions is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Doit, and thousands of servers like it.

This server

All 238 Doit tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →