Low Risk

awx_get_config

Get AWX version and configuration

Part of the Awx MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

awx-mcp-server Read Risk 2/5

AI agents call awx_get_config to retrieve information from Awx without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though awx_get_config only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-surgex-labs-awx-mcp-server.yaml
tools:
  awx_get_config:
    rules:
      - action: allow

See the full Awx policy for all 49 tools.

Tool Name awx_get_config
Category Read
MCP Server Awx MCP Server
Risk Level Low

View all 49 tools →

Agents calling read-class tools like awx_get_config have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the awx_get_config tool do? +

Get AWX version and configuration. It is categorised as a Read tool in the Awx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on awx_get_config? +

Add a rule in your Intercept YAML policy under the tools section for awx_get_config. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Awx MCP server.

What risk level is awx_get_config? +

awx_get_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit awx_get_config? +

Yes. Add a rate_limit block to the awx_get_config rule in your Intercept 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.

How do I block awx_get_config completely? +

Set action: deny in the Intercept policy for awx_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.

What MCP server provides awx_get_config? +

awx_get_config is provided by the Awx MCP server (awx-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Awx

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.