AI agents invoke longRunningOperation to trigger actions in My. 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.
The tool executes a long-running operation, which suggests it runs some process or computation. The description is vague about what the operation does, but 'long-running operation' implies active execution rather than a simple read or write. Confidence is moderate due to the lack of specific details about what is actually executed.
From the tool's definition 'long-running operation with progress notifications' — implies execution of a process or task over time
Attacks that exploit this kind of access
Demonstrates a long-running operation with progress notifications. It is categorised as a Execute tool in the My MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the My MCP server in PolicyLayer and add a rule for longRunningOperation: 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 My. Nothing to install.
longRunningOperation 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 longRunningOperation 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 longRunningOperation. 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.
longRunningOperation is provided by the My MCP server (kcbabo/everything-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →