Delete a saved Artillery configuration.
AI agents call delete_config to permanently remove resources in Artillery MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a saved configuration file, which cannot be undone. Even though the blast radius is limited to test configurations (not production systems), the irreversible data loss and the context of Artillery (a load testing tool used in CI/CD pipelines) means misconfiguration or malicious use could destroy important test setups.
From the tool's definition Tool name is 'delete_config' and description states 'Delete a saved Artillery configuration.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a saved Artillery configuration. It is categorised as a Destructive tool in the Artillery MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Artillery MCP Server MCP server in PolicyLayer and add a rule for delete_config: 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 Artillery MCP Server. Nothing to install.
delete_config 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 delete_config 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 delete_config. 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.
delete_config is provided by the Artillery MCP Server MCP server (jch1887/artillery-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 →