long_running_task

A read tool on the Sap Btp Destination MCP server.

SERVERSap Btp Destination SOURCEfacusada/mcp-btp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/facusada-mcp-btp/long-running-task.md

WHAT IT DOES

What long_running_task does on Sap Btp Destination

AI agents call long_running_task to retrieve information from Sap Btp Destination without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why long_running_task is rated Low

Even though long_running_task 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

RECOMMENDED RULE

The rule that runs long_running_task safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sap Btp Destination, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For long_running_task, this is the rule to start with:

long_running_task Allowed

long_running_task is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "long_running_task": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sap Btp Destination, apply this rule, and every long_running_task call is checked against it from then on.

FAQ

Questions about long_running_task

What does the long_running_task tool do? +

long_running_task is a read tool on the Sap Btp Destination MCP server. It is categorised as a Read tool in the Sap Btp Destination MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on long_running_task? +

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

What risk level is long_running_task? +

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

Can I rate-limit long_running_task? +

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

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

long_running_task is provided by the Sap Btp Destination MCP server (facusada/mcp-btp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sap Btp Destination, and thousands of servers like it.

This server

All 36 Sap Btp Destination tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →