List all ARC configurations stored in your repository.
AI agents call arc_list_configs to retrieve information from ARC Config MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing ARC configurations without modifying, deleting, or executing any operations. It is a simple query operation that has no blast radius if invoked by an AI agent, as it only reads and presents information already stored in the repository.
From the tool's definition Tool name is 'arc_list_configs' and description states 'List all ARC configurations stored in your repository.' The verb 'list' and action of retrieving/querying configurations indicates data retrieval with no side effects.
Attacks that exploit this kind of access
List all ARC configurations stored in your repository. It is categorised as a Read tool in the ARC Config MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ARC Config MCP Server MCP server in PolicyLayer and add a rule for arc_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 ARC Config MCP Server. Nothing to install.
arc_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 arc_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 arc_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.
arc_list_configs is provided by the ARC Config MCP Server MCP server (tsviz/arc-config-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 →