Test connectivity and system availability of Pega Infinity server using existing authentication. Makes a lightweight API call to verify the server is responding. Use authenticate_pega tool first if you need to establish authentication.
AI agents call ping_pega_service to retrieve information from Pega DX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
ping_pega_service is a diagnostic/health-check tool that retrieves system status information without side effects. It queries whether a service is available and responsive, which is a read-only operation. The low severity reflects minimal blast radius—a misused ping cannot harm data or systems, only return connectivity status information.
From the tool's definition Tool description states it 'Makes a lightweight API call to verify the server is responding' with explicit purpose to 'Test connectivity and system availability'. No data is created, modified, deleted, or financial operations are performed.
Documented attack patterns abuse exactly the kind of access ping_pega_service gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pega DX MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ping_pega_service:
{
"version": "1",
"default": "deny",
"tools": {
"ping_pega_service": {}
}
}ping_pega_service is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Test connectivity and system availability of Pega Infinity server using existing authentication. Makes a lightweight API call to verify the server is responding. Use authenticate_pega tool first if you need to establish authentication. It is categorised as a Read tool in the Pega DX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pega DX MCP Server MCP server in PolicyLayer and add a rule for ping_pega_service: 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 Pega DX MCP Server. Nothing to install.
ping_pega_service 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 ping_pega_service 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 ping_pega_service. 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.
ping_pega_service is provided by the Pega DX MCP Server MCP server (marco-looy/pega-dx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pega DX MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
65 Pega DX MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.