New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

call_destination

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

SERVERSap Btp Destination SOURCEfacusada/mcp-btp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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

Questions about call_destination

What does the call_destination tool do? +

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.

How do I enforce a policy on call_destination? +

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.

What risk level is call_destination? +

call_destination is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit call_destination? +

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.

How do I block call_destination completely? +

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.

What MCP server provides call_destination? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sap Btp Destination's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.