test_awx_connection

Test connectivity to Ansible Automation Platform controller

SERVERLogicmonitor SOURCEpypi:lm-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ryanmat-logicmonitor/test-awx-connection.md

WHAT IT DOES

What test_awx_connection does on Logicmonitor

AI agents call test_awx_connection to retrieve information from Logicmonitor without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why test_awx_connection is rated Low

Even though test_awx_connection only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs test_awx_connection safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Logicmonitor, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_awx_connection, this is the rule to start with:

test_awx_connection Allowed

test_awx_connection is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_awx_connection": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Logicmonitor, apply this rule, and every test_awx_connection call is checked against it from then on.

FAQ

Questions about test_awx_connection

What does the test_awx_connection tool do? +

Test connectivity to Ansible Automation Platform controller. It is categorised as a Read tool in the Logicmonitor MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on test_awx_connection? +

Register the Logicmonitor MCP server in PolicyLayer and add a rule for test_awx_connection: 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 Logicmonitor. Nothing to install.

What risk level is test_awx_connection? +

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

Can I rate-limit test_awx_connection? +

Yes. Add a rate_limit block to the test_awx_connection 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.

How do I block test_awx_connection completely? +

Set action: deny in the PolicyLayer policy for test_awx_connection. 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 test_awx_connection? +

test_awx_connection is provided by the Logicmonitor MCP server (pypi:lm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Logicmonitor, and thousands of servers like it.

This server

All 306 Logicmonitor tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →