Create a new asset folder.
AI agents use wiki_asset_create_folder to create or update resources in Mcp Wikijs Mv — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Wikijs Mv environment.
Creating a folder is a write operation that modifies the asset structure by adding a new organizational container. This is reversible (the folder can be deleted) and has no permanent destructive effects. Severity is medium because folder creation has limited blast radius—it organizes assets but doesn't modify or delete existing data, and folder naming issues are easily corrected.
From the tool's definition Tool description states 'Create a new asset folder' - this creates a new resource (folder) in the wiki asset system, which is a reversible write operation.
Attacks that exploit this kind of access
Create a new asset folder. It is categorised as a Write tool in the Mcp Wikijs Mv MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Wikijs Mv MCP server in PolicyLayer and add a rule for wiki_asset_create_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 Wikijs Mv. Nothing to install.
wiki_asset_create_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 wiki_asset_create_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 wiki_asset_create_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.
wiki_asset_create_folder is provided by the Mcp Wikijs Mv MCP server (janschachtschabel/mcp-for-wiki-js). 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 →