set_drive_owners

Replace owners on an existing Drive. Owners accept account UUIDs, exact emails, or exact person names. By default, each owner is also ensured as a Drive member. Pass owners=[] to clear owners.

SERVERHuly SOURCE@firfi/huly-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/set-drive-owners.md

WHAT IT DOES

What set_drive_owners does on Huly

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

RISK

Why set_drive_owners is rated Medium

This tool modifies ownership permissions on a Drive resource, which is a reversible write operation. While it affects access control (a sensitive function), it does not delete data or trigger destructive operations—owners can be re-assigned.

From the tool's definition Tool description states 'Replace owners on an existing Drive' and 'Pass owners=[] to clear owners', indicating modification of access control and ownership metadata on existing resources.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_drive_owners safely

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

set_drive_owners Rate-limited

set_drive_owners 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": {
    "set_drive_owners": {
      "limits": [
        {
          "counter": "set_drive_owners_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 Huly, apply this rule, and every set_drive_owners call is checked against it from then on.

FAQ

Questions about set_drive_owners

What does the set_drive_owners tool do? +

Replace owners on an existing Drive. Owners accept account UUIDs, exact emails, or exact person names. By default, each owner is also ensured as a Drive member. Pass owners=[] to clear owners. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_drive_owners? +

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

What risk level is set_drive_owners? +

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

Can I rate-limit set_drive_owners? +

Yes. Add a rate_limit block to the set_drive_owners 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 set_drive_owners completely? +

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

set_drive_owners is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

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