AI agents use element_create to create or update resources in Voog — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Voog environment.
This tool creates new content elements in a Voog CMS instance. Creation operations are reversible (elements can be deleted), so this falls under Write rather than Destructive. The severity is medium because misuse could create unwanted elements polluting the site structure, but the impact is bounded to new content creation without cascading effects or data loss.
From the tool's definition Tool name 'element_create' and description 'Create an element (POST /elements)' indicate a POST operation that generates new data in the CMS. The flat body structure suggests straightforward element creation without complex nesting.
Attacks that exploit this kind of access
Create an element (POST /elements). Body is FLAT. It is categorised as a Write tool in the Voog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Voog MCP server in PolicyLayer and add a rule for element_create: 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 Voog. Nothing to install.
element_create 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 element_create 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 element_create. 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.
element_create is provided by the Voog MCP server (runnel/voog-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 →