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

auto_updateUnit

Rename, describe or move a unit (PATCH /v1/auto/units/{unit})

SERVERGenesis SOURCE@onesi/genesis-mcp
Medium RISK CLASS
Category Write
Parameters 33 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/onesi-genesis-mcp/auto-updateunit.md

What auto_updateUnit does on Genesis

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

ParameterTypeRequiredDescription
body object Yes At least one of name, description or parent_id.
unit string Yes Unit id (unit_...)
if_match string | integer Yes The version you read (the `version` field of the object you are changing, or its ETag); a stale version is a 409

Parameters from the server's own tool schema.

Why auto_updateUnit is rated Medium

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

Risk signalsAccepts raw HTML/template content (body)

Questions about auto_updateUnit

What does the auto_updateUnit tool do? +

Rename, describe or move a unit (PATCH /v1/auto/units/{unit}). It is categorised as a Write tool in the Genesis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does auto_updateUnit accept? +

auto_updateUnit accepts 3 parameters: body, unit, if_match. Required: body, unit, if_match. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on auto_updateUnit? +

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

What risk level is auto_updateUnit? +

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

Can I rate-limit auto_updateUnit? +

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

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

auto_updateUnit is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Genesis, and thousands of servers like it.

Across the catalogue

// 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 Genesis'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.