AI agents use category_update 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 modifies existing ecommerce category data reversibly via an update operation. It does not delete data (which would be Destructive) nor execute arbitrary code (Execute). The 'high' severity reflects that misuse could corrupt product category configurations affecting customer-facing ecommerce operations, inventory organization, and business logic.
From the tool's definition PUT /admin/api/ecommerce/v1/categories/ — indicates HTTP PUT request for updating a category resource. The tool name 'category_update' and description explicitly state it updates (modifies) a category.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Update a category (PUT /admin/api/ecommerce/v1/categories/. 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 category_update: 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.
category_update 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 category_update 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 category_update. 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.
category_update 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 →