AI agents use insert_items 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.
The tool creates or adds items to Dynalist documents, which is a Write operation—reversible modifications that do not execute code or delete data. Confidence is moderate (0.75) rather than high because the tool description contains a placeholder ('${INSTRUCTIONS_FIRST_GUIDANCE}') that does not provide specific details about constraints or scope, limiting full clarity on potential impacts.
From the tool's definition Tool name 'insert_items' indicates creation of new content. Server description states the MCP enables 'write...Dynalist documents programmatically.' The sibling tools include 'create_document', 'create_folder', 'edit_items', and 'delete_items', positioning…
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 insert_items: 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.
insert_items 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 insert_items 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 insert_items. 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.
insert_items 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 →