long-running-ping
A read tool on the Mcp Test Servers MCP server.
This record as markdown: /tools/mcp-test-servers/long-running-ping.md
What long-running-ping does on Mcp Test Servers
AI agents call long-running-ping to retrieve information from Mcp Test Servers without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why long-running-ping is rated Low
Even though long-running-ping 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
The rule that runs long-running-ping safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Test Servers, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For long-running-ping, this is the rule to start with:
long-running-ping is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Test Servers, apply this rule, and every long-running-ping call is checked against it from then on.
Questions about long-running-ping
long-running-ping is a read tool on the Mcp Test Servers MCP server. It is categorised as a Read tool in the Mcp Test Servers MCP Server, which means it retrieves data without modifying state.
Register the Mcp Test Servers MCP server in PolicyLayer and add a rule for long-running-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 Mcp Test Servers. Nothing to install.
long-running-ping 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 long-running-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 long-running-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.
long-running-ping is provided by the Mcp Test Servers MCP server (msfeldstein/mcp-test-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Test Servers, and thousands of servers like it.
This server
Across the catalogue