long_running_operation · MCP Everything MCP: Risk & Policy

WHAT IT DOES

What long_running_operation does on MCP Everything

AI agents invoke long_running_operation to trigger actions in MCP Everything. 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 IT NEEDS A POLICY

Why long_running_operation needs a policy

The name implies executing a long-running operation, which typically falls under Execute category. However, without a description, the exact nature is unknown. Given the test server context and sibling tools (add, echo, print_env, sample_llm), this is likely a demonstration tool for testing async/long-running MCP features. Confidence is low due to the empty description.

From the tool's definition Tool name 'long_running_operation' suggests execution of some prolonged process, but the description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

long_running_operation Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "long_running_operation": {
      "limits": [
        {
          "counter": "long_running_operation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Everything, so you can run agents against it safely.

FAQ

Questions about long_running_operation

What does the long_running_operation tool do? +

long_running_operation. It is categorised as a Execute tool in the MCP Everything MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on long_running_operation? +

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

What risk level is long_running_operation? +

long_running_operation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit long_running_operation? +

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

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

long_running_operation is provided by the MCP Everything MCP server (s2005/mcp-everything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.