call_destination
Call the target URL of a resolved destination using its auth token.
This record as markdown: /tools/facusada-mcp-btp/call-destination.md
What call_destination does on Sap Btp Destination
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.
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 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
Attacks that exploit this kind of access
The rule that runs call_destination 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 call_destination, this is the rule to start with:
call_destination 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap Btp Destination, apply this rule, and every call_destination call is checked against it from then on.
Questions about call_destination
Call the target URL of a resolved destination using its auth token. It is categorised as a Execute tool in the Sap Btp Destination MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sap Btp Destination MCP server in PolicyLayer and add a rule for call_destination: 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.
call_destination 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 call_destination 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 call_destination. 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.
call_destination 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.
More on Sap Btp Destination, and thousands of servers like it.
Across the catalogue