update_people_group · Mycase MCP: Risk & Policy

WHAT IT DOES

What update_people_group does on Mycase

AI agents use update_people_group 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_people_group needs a policy

Renaming a people group is a metadata modification that changes existing data but remains reversible—the old name can be restored. This is clearly a Write operation. Severity is low because the blast radius of misuse is limited to organizational grouping metadata, with no financial impact, destructive consequences, or external side effects. The tool operates within the MyCase case management system's data model.

From the tool's definition Tool performs 'Rename a people group' which modifies data (the group name) in a reversible manner. The action is explicitly an update operation, not creation, deletion, or execution of external code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_people_group Rate-limited

update_people_group 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_people_group": {
      "limits": [
        {
          "counter": "update_people_group_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_people_group

What does the update_people_group tool do? +

Rename a people group. 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_people_group? +

Register the Mycase MCP server in PolicyLayer and add a rule for update_people_group: 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_people_group? +

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

Can I rate-limit update_people_group? +

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

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

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