Create a new field in a collection
AI agents use create_field to create or update resources in Directus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Directus MCP Server environment.
Creating a field modifies the collection schema reversibly (fields can be deleted or altered later), making it a Write action rather than Destructive. However, the severity is high because schema modifications can have cascading effects on dependent queries, workflows, and permissions, and an AI agent could inadvertently break application logic by adding incompatible field types or names that conflict with existing…
From the tool's definition Tool name is 'create_field' and description states 'Create a new field in a collection' — this directly creates/modifies schema structure within the Directus CMS.
Attacks that exploit this kind of access
Create a new field in a collection. It is categorised as a Write tool in the Directus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Directus MCP Server MCP server in PolicyLayer and add a rule for create_field: 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 Directus MCP Server. Nothing to install.
create_field 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_field 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_field. 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_field is provided by the Directus MCP Server MCP server (staminna/mcp-server-claude). 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 →