long_running_progress

A other tool on the Mcp Test Servers MCP server.

SERVERMcp Test Servers SOURCEmsfeldstein/mcp-test-servers

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-test-servers/long-running-progress.md

WHAT IT DOES

What long_running_progress does on Mcp Test Servers

AI agents call long_running_progress as a supporting operation in Mcp Test Servers workflows.

RISK

Why long_running_progress is rated Low

The description is empty, providing no information about what this tool does. The name 'long_running_progress' suggests it may report or track progress of a long-running operation (a Read-like behavior), but without any description, the exact category cannot be determined. Defaulting to Other with low confidence due to lack of evidence.

From the tool's definition Tool name is 'long_running_progress' and description is empty/uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs long_running_progress 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_progress, this is the rule to start with:

long_running_progress Rate-limited

long_running_progress gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "long_running_progress": {
      "limits": [
        {
          "counter": "long_running_progress_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about long_running_progress

What does the long_running_progress tool do? +

long_running_progress is a other tool on the Mcp Test Servers MCP server. It is categorised as a Other tool in the Mcp Test Servers MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on long_running_progress? +

Register the Mcp Test Servers MCP server in PolicyLayer and add a rule for long_running_progress: 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.

What risk level is long_running_progress? +

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

Can I rate-limit long_running_progress? +

Yes. Add a rate_limit block to the long_running_progress 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 long_running_progress completely? +

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

long_running_progress 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.

KEEP EXPLORING

More on Mcp Test Servers, and thousands of servers like it.

This server

All 67 Mcp Test Servers tools →

Across the catalogue

log_progress on Agent Jail → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →