Reorder categories in a Docs collection
AI agents use docs_update_category_order to create or update resources in MCP Help Scout — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Help Scout environment.
Reordering categories changes their display order in a collection but does not delete or irreversibly destroy any data. The operation can be undone by reordering again, making it a Write rather than Destructive action. Misuse could disrupt knowledge base navigation but has limited blast radius.
From the tool's definition 'Reorder categories in a Docs collection' — this modifies the ordering/arrangement of existing categories, which is a reversible write operation
Attacks that exploit this kind of access
Reorder categories in a Docs collection. It is categorised as a Write tool in the MCP Help Scout MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Help Scout MCP server in PolicyLayer and add a rule for docs_update_category_order: 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 MCP Help Scout. Nothing to install.
docs_update_category_order 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 docs_update_category_order 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 docs_update_category_order. 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.
docs_update_category_order is provided by the MCP Help Scout MCP server (solveitsimply/mcp-helpscout). 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 →