Create a new case (unit of work) and set it as active. A case represents a bounded piece of work: feature, bugfix, refactor, spike. Creating a case provides context for logging pressure events.
AI agents use create_case to create or update resources in Decision OS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Decision OS MCP environment.
This tool creates and modifies system state by adding a new case record and setting it as the active context. While cases can likely be closed or archived, the act of creation is a Write operation that persists data.
From the tool's definition Tool creates a new case, which is a persistent record in the decision tracking system. The description states 'Create a new case (unit of work) and set it as active', indicating irreversible creation and state modification of system entities.
Attacks that exploit this kind of access
Create a new case (unit of work) and set it as active. A case represents a bounded piece of work: feature, bugfix, refactor, spike. Creating a case provides context for logging pressure events. It is categorised as a Write tool in the Decision OS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Decision OS MCP server in PolicyLayer and add a rule for create_case: 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 Decision OS MCP. Nothing to install.
create_case 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 create_case 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 create_case. 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.
create_case is provided by the Decision OS MCP server (marianstefi20/decision-os-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →