// SCAN REPORT

Sap Btp Destination

36 tools. 20 can modify or destroy data without limits.

10 write tools that can modify data. Rate limits recommended.

Last updated: 14 Aug 2026

20 can modify or destroy data

16 read-only

36 tools total

Community server · catalogue entry checked 14/08/2026

How to control Sap Btp Destination ↓

TOOL MAP

What Sap Btp Destination exposes to your agents

Read (16) Write / Execute (10) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Sap Btp Destination tools

Execute · Critical run_query The tool name 'run_query' combined with context (SAP BTP, destinations, financial sibling tools) indicates code or command execution rather than read-only retrieval. Execute · High call_destination This tool executes outbound HTTP requests to external/backend systems using resolved authentication tokens from SAP BTP destinations. Write · Medium add The name 'add' typically indicates a creation or modification operation (Write category). Write · Medium add_expense The tool name 'add_expense' suggests it creates or adds a new expense entry, which is a reversible write operation on financial data.

20 of Sap Btp Destination's 36 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Sap Btp Destination

PolicyLayer is an MCP gateway — it sits between your AI agents and Sap Btp Destination, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "add": {
    "limits": [
      {
        "counter": "add_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_worker_status": {
    "limits": [
      {
        "counter": "check_worker_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Sap Btp Destination — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SAP BTP DESTINATION →

Instant setup, no code required.

FULL CATALOGUE

All 36 Sap Btp Destination tools

EXECUTE 2 tools

Execute call_destination Call the target URL of a resolved destination using its auth token. Execute run_query run_query

WRITE 8 tools

Write add add Write add_expense add_expense Write save save Write save_contact save_contact Write schedule_task schedule_task Write store_data store_data Write store_files Store uploaded files. Receives file objects with name, size, type, data (base64). Write submit_form Validate and process form submission.

READ 16 tools

Read check_worker_status check_worker_status Read echo_tool Echo the input text Read get_auth_type get_auth_type Read get_client_ip get_client_ip Read get_destination Resolve a destination by name using SAP BTP Destination Service. Read get_info Provides a simple info. Read get_my_emails get_my_emails Read get_user_id get_user_id Read healthcheck Return the application status and whether SAP credentials are configured. Read introspect introspect Read list_files List all uploaded files with metadata. Read log_progress log_progress Read long_running_task long_running_task Read read_file Read an uploaded file's contents by name. Read read_write_tool read_write_tool Read tool_with_context tool_with_context

OTHER 10 tools

Other admin_tool admin_tool Other async_tool async_tool Other custom_name custom_name Other flexible_task flexible_task Other greet greet Other greeting greeting Other multiply multiply Other my_task my_task Other my_tool my_tool Other protected_tool protected_tool

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Sap Btp Destination

How do I prevent bulk modifications through Sap Btp Destination? +

The Sap Btp Destination server has 8 write tools including add, add_expense, save. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Sap Btp Destination.

How many tools does the Sap Btp Destination MCP server expose? +

36 tools across 3 categories: Execute, Read, Write. 16 are read-only. 20 can modify, create, or delete data.

How do I enforce a policy on Sap Btp Destination? +

Register the Sap Btp Destination MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Sap Btp Destination tool call.

Deterministic rules across all 36 Sap Btp Destination tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SAP BTP DESTINATION →

Instant setup, no code required.

36 Sap Btp Destination tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Sap Btp Destination's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →