get_destination

What get_destination does on Sap Btp Destination

AI agents call get_destination 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.

Why get_destination is rated Low

This tool retrieves destination configurations from SAP BTP, which is fundamentally a read operation. However, severity is medium rather than low because destination configurations may contain sensitive data such as credentials, API keys, connection strings, or authentication tokens. If an agent calls this with an attacker-controlled destination name, it could leak secrets.

From the tool's definition The tool description explicitly states it 'Resolve[s] a destination by name' - a retrieval operation. The server description confirms it 'reads Destination Service configurations', categorizing this as a query/fetch operation with no mutation.

The rule that runs get_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 get_destination, this is the rule to start with:

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

Questions about get_destination