auto_updateMandate

Update a mandate or move its status (PATCH /v1/auto/mandates/{mandate})

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-updatemandate.md

WHAT IT DOES

What auto_updateMandate does on Genesis

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

Parameter	Type	Required	Description
`body`	object	Yes	At least one field other than reason.
`mandate`	string	Yes	Mandate id (mnd_...)
`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.

RISK

Why auto_updateMandate is rated Medium

An AI agent can call auto_updateMandate 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) · High parameter count (27 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs auto_updateMandate safely

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

auto_updateMandate Rate-limited

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

FAQ

Questions about auto_updateMandate

What does the auto_updateMandate tool do? +

Update a mandate or move its status (PATCH /v1/auto/mandates/{mandate}). 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_updateMandate accept? +

auto_updateMandate accepts 3 parameters: body, mandate, if_match. Required: body, mandate, 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_updateMandate? +

Register the Genesis MCP server in PolicyLayer and add a rule for auto_updateMandate: 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_updateMandate? +

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

Can I rate-limit auto_updateMandate? +

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

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

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

KEEP EXPLORING

More on Genesis, and thousands of servers like it.

This server

All 1127 Genesis tools →

Across the catalogue

The MCP Attack Database →

Guides

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