List all saved Artillery configurations.
AI agents call list_configs to retrieve information from Artillery MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns saved configurations without modifying, creating, deleting, or executing anything. It is a straightforward data retrieval operation with minimal security impact if misused by an AI agent—the worst outcome would be information disclosure about existing test configurations.
From the tool's definition Tool name 'list_configs' and description 'List all saved Artillery configurations' indicate a retrieval operation with no side effects. The verb 'list' is explicitly mentioned in the Read category definition.
Attacks that exploit this kind of access
List all saved Artillery configurations. It is categorised as a Read tool in the Artillery MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Artillery MCP Server MCP server in PolicyLayer and add a rule for list_configs: 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.
list_configs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_configs 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 list_configs. 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.
list_configs 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 →