# call_destination

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

Agent View of the PolicyLayer registry record for `call_destination`. HTML page: https://policylayer.com/tools/facusada-mcp-btp/call-destination

## Facts

- Tool: `call_destination`
- Server: Sap Btp Destination (`facusada/mcp-btp`) — https://policylayer.com/tools/facusada-mcp-btp.md
- Homepage: https://github.com/facusada/mcp-btp
- Risk category: Execute (High risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "call_destination",
    "arguments": {}
  }
}
```

## Why call_destination is rated High

This tool executes outbound HTTP requests to external/backend systems using resolved authentication tokens from SAP BTP destinations. It is not merely reading configuration — it performs live calls to target URLs with auth tokens, which can trigger arbitrary operations (data reads, writes, transactions, etc.) depending on the destination.

From the tool's own definition: "'Call the target URL of a resolved destination using its auth token' — actively triggers an HTTP call to an external system using authenticated credentials"

## Use case

AI agents invoke call_destination to trigger actions in Sap Btp Destination. 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Sap Btp Destination:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_destination": {
      "limits": [
        {
          "counter": "call_destination_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Sap Btp Destination (35)

- `run_query` — Execute — https://policylayer.com/tools/facusada-mcp-btp/run-query.md
- `admin_tool` — Other — https://policylayer.com/tools/facusada-mcp-btp/admin-tool.md
- `async_tool` — Other — https://policylayer.com/tools/facusada-mcp-btp/async-tool.md
- `custom_name` — Other — https://policylayer.com/tools/facusada-mcp-btp/custom-name.md
- `flexible_task` — Other — https://policylayer.com/tools/facusada-mcp-btp/flexible-task.md
- `greet` — Other — https://policylayer.com/tools/facusada-mcp-btp/greet.md
- `greeting` — Other — https://policylayer.com/tools/facusada-mcp-btp/greeting.md
- `multiply` — Other — https://policylayer.com/tools/facusada-mcp-btp/multiply.md
- `my_task` — Other — https://policylayer.com/tools/facusada-mcp-btp/my-task.md
- `my_tool` — Other — https://policylayer.com/tools/facusada-mcp-btp/my-tool.md
- `protected_tool` — Other — https://policylayer.com/tools/facusada-mcp-btp/protected-tool.md
- `check_worker_status` — Read — https://policylayer.com/tools/facusada-mcp-btp/check-worker-status.md
- `echo_tool` — Read — https://policylayer.com/tools/facusada-mcp-btp/echo-tool.md
- `get_auth_type` — Read — https://policylayer.com/tools/facusada-mcp-btp/get-auth-type.md
- `get_client_ip` — Read — https://policylayer.com/tools/facusada-mcp-btp/get-client-ip.md
- `get_destination` — Read — https://policylayer.com/tools/facusada-mcp-btp/get-destination.md
- `get_info` — Read — https://policylayer.com/tools/facusada-mcp-btp/get-info.md
- `get_my_emails` — Read — https://policylayer.com/tools/facusada-mcp-btp/get-my-emails.md
- `get_user_id` — Read — https://policylayer.com/tools/facusada-mcp-btp/get-user-id.md
- `healthcheck` — Read — https://policylayer.com/tools/facusada-mcp-btp/healthcheck.md
- `introspect` — Read — https://policylayer.com/tools/facusada-mcp-btp/introspect.md
- `list_files` — Read — https://policylayer.com/tools/facusada-mcp-btp/list-files.md
- `log_progress` — Read — https://policylayer.com/tools/facusada-mcp-btp/log-progress.md
- `long_running_task` — Read — https://policylayer.com/tools/facusada-mcp-btp/long-running-task.md
- `read_file` — Read — https://policylayer.com/tools/facusada-mcp-btp/read-file.md
- `read_write_tool` — Read — https://policylayer.com/tools/facusada-mcp-btp/read-write-tool.md
- `tool_with_context` — Read — https://policylayer.com/tools/facusada-mcp-btp/tool-with-context.md
- `add` — Write — https://policylayer.com/tools/facusada-mcp-btp/add.md
- `add_expense` — Write — https://policylayer.com/tools/facusada-mcp-btp/add-expense.md
- `save` — Write — https://policylayer.com/tools/facusada-mcp-btp/save.md
- …and 5 more: https://policylayer.com/tools/facusada-mcp-btp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=facusada-mcp-btp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/facusada-mcp-btp