get_user_id
A read tool on the Sap Btp Destination MCP server.
This record as markdown: /tools/facusada-mcp-btp/get-user-id.md
What get_user_id does on Sap Btp Destination
AI agents call get_user_id 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_user_id is rated Low
This tool appears to fetch user identification data from the SAP BTP system. It performs a query/retrieval operation with no side effects, no code execution, no destructive actions, and no financial operations. The low severity reflects that user ID retrieval alone has limited blast radius unless misused downstream in conjunction with other tools.
From the tool's definition Tool name 'get_user_id' indicates retrieval of user identity information with no modification capability. Description is empty, but naming convention and context within a BTP destination service server suggest this retrieves user identity data.
Attacks that exploit this kind of access
The rule that runs get_user_id 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_user_id, this is the rule to start with:
get_user_id is read-only, so it stays allowed. 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 get_user_id call is checked against it from then on.
Questions about get_user_id
get_user_id is a read tool on the Sap Btp Destination MCP server. It is categorised as a Read tool in the Sap Btp Destination MCP Server, which means it retrieves data without modifying state.
Register the Sap Btp Destination MCP server in PolicyLayer and add a rule for get_user_id: 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.
get_user_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_user_id 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 get_user_id. 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.
get_user_id 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.
This server
Across the catalogue