AI agents use create_folder to create or update resources in Dynalist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dynalist environment.
Creating a folder is a write operation that creates new organizational structure in Dynalist documents. It is reversible (folders can be deleted) and has limited blast radius. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. Medium severity reflects that unintended folder creation could clutter document structure but remains easily correctable.
From the tool's definition Tool name 'create_folder' and server description indicating 'write' capability to 'organize Dynalist documents programmatically.' The tool description references '${INSTRUCTIONS_FIRST_GUIDANCE}' which is uninformative, but context from sibling tools…
Attacks that exploit this kind of access
${INSTRUCTIONS_FIRST_GUIDANCE}. It is categorised as a Write tool in the Dynalist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dynalist MCP server in PolicyLayer and add a rule for 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 Dynalist. Nothing to install.
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 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 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.
create_folder is provided by the Dynalist MCP server (wawworld/dynalist-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 →