Query all configs under a namespace/environment/cluster in Apollo.
AI agents call apollo_get_namespace_configs to retrieve information from Mcp Apollo Config without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves configuration data from Apollo Config Center without side effects. However, the severity is elevated from 'low' to 'medium' because configuration data often contains sensitive information (API keys, database credentials, secrets), and exposing all configs in a namespace could leak security-critical details if an agent mishandles the query scope or leaks results.
From the tool's definition Tool name includes 'get' and description states 'Query all configs' with no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
Query all configs under a namespace/environment/cluster in Apollo. It is categorised as a Read tool in the Mcp Apollo Config MCP Server, which means it retrieves data without modifying state.
Register the Mcp Apollo Config MCP server in PolicyLayer and add a rule for apollo_get_namespace_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 Mcp Apollo Config. Nothing to install.
apollo_get_namespace_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 apollo_get_namespace_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 apollo_get_namespace_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.
apollo_get_namespace_configs is provided by the Mcp Apollo Config MCP server (xsg22/mcp-apollo-config). 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 →