Update multiple panels in Directus at once. Each panel must include an id field. Example: {panels: [{id:
AI agents use update_panels 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 dashboard panel configurations reversibly (panels can be updated again or reverted), which fits the Write category. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or retrieve data read-only (Read).
From the tool's definition Tool name 'update_panels' and description 'Update multiple panels in Directus at once' indicate modification of existing dashboard panel configurations without deletion or creation of new entities.
Attacks that exploit this kind of access
Update multiple panels in Directus at once. Each panel must include an id field. Example: {panels: [{id:. 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_panels: 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_panels 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_panels 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_panels. 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_panels is provided by the Directus MCP Server MCP server (skeyelab/directus-mcp-server). 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 →