Retrieve a saved Artillery configuration by name.
AI agents call get_config 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 an existing configuration object without side effects. It performs no modifications, executions, or destructive actions. The blast radius of misuse is minimal—an attacker could only view the contents of a saved config file, which may contain sensitive test parameters but does not directly execute code or delete data.
From the tool's definition Tool name is 'get_config' and description states 'Retrieve a saved Artillery configuration by name.' The verb 'retrieve' and the read-only nature of fetching an existing configuration without modification or execution indicate a pure data retrieval operation.
Attacks that exploit this kind of access
Retrieve a saved Artillery configuration by name. 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 get_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.
get_config 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 get_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 get_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.
get_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 →