Update an existing field in a collection
AI agents use update_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.
This tool modifies field definitions within a Directus CMS collection, which is a write operation. It changes schema metadata but does not delete data irreversibly or execute arbitrary code. The impact is moderate because field updates could affect data validation, storage, or display, but the changes remain reversible through subsequent updates.
From the tool's definition Tool name: 'update_field'. Description: 'Update an existing field in a collection'. The verb 'update' and the action of modifying an existing field indicate reversible data modification.
Attacks that exploit this kind of access
Update an existing 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 update_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.
update_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 update_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 update_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.
update_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 →