Reset a QIT test environment
AI agents call reset_environment to permanently remove resources in QIT MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While 'reset' might seem like a Write operation, in the context of test environments, a reset is fundamentally a destructive action that irreversibly clears the environment's state, data, and configurations. This cannot be undone without restoring from a backup.
From the tool's definition Tool name is 'reset_environment' with description 'Reset a QIT test environment'. Reset operations on test environments typically involve wiping data, clearing state, and removing configurations—actions that cannot be easily reversed without backups.
Attacks that exploit this kind of access
Reset a QIT test environment. It is categorised as a Destructive tool in the QIT MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the QIT MCP Server MCP server in PolicyLayer and add a rule for reset_environment: 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 QIT MCP Server. Nothing to install.
reset_environment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reset_environment 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 reset_environment. 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.
reset_environment is provided by the QIT MCP Server MCP server (woocommerce/qit-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 →