scopes_updateTask
Update a task or move its status (PATCH /v1/scopes/tasks/{task})
This record as markdown: /tools/onesi-genesis-mcp/scopes-updatetask.md
What scopes_updateTask does on Genesis
AI agents use scopes_updateTask 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 force and reason. |
task | string | Yes | Task id (tsk_...) or identifier such as ENG-12 |
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 scopes_updateTask is rated Medium
An AI agent can call scopes_updateTask 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 (14 properties)
Attacks that exploit this kind of access
The rule that runs scopes_updateTask 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 scopes_updateTask, this is the rule to start with:
scopes_updateTask 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every scopes_updateTask call is checked against it from then on.
Questions about scopes_updateTask
Update a task or move its status (PATCH /v1/scopes/tasks/{task}). 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.
scopes_updateTask accepts 3 parameters: body, task, if_match. Required: body, task, if_match. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for scopes_updateTask: 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.
scopes_updateTask is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the scopes_updateTask 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.
Set action: deny in the PolicyLayer policy for scopes_updateTask. 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.
scopes_updateTask 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.
This server
Across the catalogue