New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

set_space_owners

Replace owners on an existing Huly space. Owners accept account UUID, exact email, or exact person display name. By default, owners are also ensured in members.

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-space-owners.md

What set_space_owners does on Huly

AI agents use set_space_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.

Why set_space_owners is rated Medium

This tool modifies access control metadata (space owners) on an existing resource. While it affects permissions and could have significant blast radius if misused by an agent (potentially locking out legitimate users or granting unauthorized administrative access), it is reversible—owners can be replaced again.

From the tool's definition Tool description states 'Replace owners on an existing Huly space' - this is a modification operation that changes ownership permissions on a space resource.

Questions about set_space_owners

What does the set_space_owners tool do? +

Replace owners on an existing Huly space. Owners accept account UUID, exact email, or exact person display name. By default, owners are also ensured in members. 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_space_owners? +

Register the Huly MCP server in PolicyLayer and add a rule for set_space_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_space_owners? +

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

Can I rate-limit set_space_owners? +

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

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

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

More on Huly, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.