AI agents use create-media-type-folder to create or update resources in Mcp Dev — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Dev environment.
This tool creates a new organizational structure element (a folder) within the CMS. The operation is reversible (the folder can be deleted), affects only metadata/organizational structures rather than actual content or system resources, and has a limited blast radius if misused. It aligns with the Write category as a creation operation with no side effects beyond the reversible addition of a folder entity.
From the tool's definition The tool name includes 'create' and the description states 'Creates a new media type folder', indicating the tool creates a new entity in the Umbraco CMS.
Attacks that exploit this kind of access
Creates a new media type folder. It is categorised as a Write tool in the Mcp Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for create-media-type-folder: 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 Mcp Dev. Nothing to install.
create-media-type-folder 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-media-type-folder 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-media-type-folder. 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-media-type-folder is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). 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 →