update_case_stage · Mycase MCP: Risk & Policy

WHAT IT DOES

What update_case_stage does on Mycase

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

WHY IT NEEDS A POLICY

Why update_case_stage needs a policy

This tool modifies case stage data in a law firm's case management system. While the change is reversible (a stage can be renamed again), it affects case organization and potentially visibility/workflow. The impact is limited to metadata about a case stage rather than core case data or destructive operations. This is a Write operation: modifying data without irreversible consequences.

From the tool's definition Tool name: 'update_case_stage' with description 'Rename a case stage.' The verb 'update' combined with 'rename' indicates modification of existing data (a case stage name).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_case_stage Rate-limited

update_case_stage 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": {
    "update_case_stage": {
      "limits": [
        {
          "counter": "update_case_stage_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mycase, so you can run agents against it safely.

FAQ

Questions about update_case_stage

What does the update_case_stage tool do? +

Rename a case stage. It is categorised as a Write tool in the Mycase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_case_stage? +

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

What risk level is update_case_stage? +

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

Can I rate-limit update_case_stage? +

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

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

update_case_stage is provided by the Mycase MCP server (rosenadvertising/mycase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.