AI agents use create_case_subfolder 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 creates (writes) new data structures in the form of case subfolders. It does not execute code, trigger external operations, delete data irreversibly, or move money. The blast radius is minimal—a mistakenly created folder is easily removed and causes no cascading damage to the law firm's case management system.
From the tool's definition Tool name 'create_case_subfolder' and description 'Create a subfolder within a case' indicate creation of a new folder structure. The action is reversible (folders can be deleted) and produces no side effects beyond the folder creation itself.
Attacks that exploit this kind of access
Create a subfolder within a case. path: relative path, e.g. 'Contracts/2026'. 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_case_subfolder: 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_case_subfolder 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_subfolder 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_subfolder. 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_subfolder 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 →