cx_ping
Ping a destination from a CX switch and return the result (async, polls ~60s).
This record as markdown: /tools/secure-ssid-centralmcp/cx-ping.md
What cx_ping does on API-Central
AI agents invoke cx_ping to trigger actions in API-Central. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why cx_ping is rated High
This tool executes a network diagnostic command (ping) on a CX switch. It triggers an external operation on network infrastructure. While ping is generally read-only in nature, it executes a command on a remote device and involves polling, making it an Execute category action. Misuse could flood a network target or reveal network topology, but blast radius is moderate.
From the tool's definition Ping a destination from a CX switch and return the result (async, polls ~60s)
Attacks that exploit this kind of access
The rule that runs cx_ping safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cx_ping, this is the rule to start with:
cx_ping stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every cx_ping call is checked against it from then on.
Questions about cx_ping
Ping a destination from a CX switch and return the result (async, polls ~60s). It is categorised as a Execute tool in the API-Central MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the API-Central MCP server in PolicyLayer and add a rule for cx_ping: 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 API-Central. Nothing to install.
cx_ping is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cx_ping 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 cx_ping. 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.
cx_ping is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API-Central, and thousands of servers like it.
Across the catalogue