AI agents use update_practice_area 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.
This tool modifies existing data (practice area metadata) in a reversible manner. Renaming a practice area does not delete data or trigger external operations, making it a Write category action. Severity is medium because incorrect renaming could cause confusion across case categorization and billing, but the change is easily reversible and has limited blast radius compared to destructive or financial operations.
From the tool's definition Tool description states 'Rename a practice area' which is a modification operation. The sibling tools include create_case, create_client, and other data-creation operations, confirming this server manages organizational data.
Attacks that exploit this kind of access
Rename a practice area. 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.
Register the Mycase MCP server in PolicyLayer and add a rule for update_practice_area: 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.
update_practice_area 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 update_practice_area 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 update_practice_area. 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.
update_practice_area 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.
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 →