AI agents use create_location 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.
Creating a location is a reversible write operation that adds data to the system. It does not execute external code, delete data, move money, or trigger irreversible actions. The blast radius is low since location creation is a routine administrative task with minimal downstream impact on case management, clients, or financial operations. The operation can be easily undone via deletion or modification.
From the tool's definition Tool name 'create_location' and description 'Create a new location' indicate data creation. The sibling tools (create_case, create_case_note, create_call) all perform write operations on law firm management data.
Attacks that exploit this kind of access
Create a new location. 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 create_location: 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.
create_location 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_location 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_location. 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_location 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 →