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

get_user_id

A read tool on the Sap Btp Destination MCP server.

SERVERSap Btp Destination SOURCEfacusada/mcp-btp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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.

Questions about get_user_id

What does the get_user_id tool do? +

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.

How do I enforce a policy on get_user_id? +

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.

What risk level is get_user_id? +

get_user_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_user_id? +

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.

How do I block get_user_id completely? +

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.

What MCP server provides get_user_id? +

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.

// 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.