get_user_info
Get information about the authenticated user
This record as markdown: /tools/delano-postman-mcp-server/get-user-info.md
What get_user_info does on Postman
AI agents call get_user_info to retrieve information from Postman 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_info is rated Low
This tool retrieves user information from an authenticated session. It performs a query operation that returns data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an attacker gains only read access to user metadata. This is a straightforward Read category classification.
From the tool's definition Tool name 'get_user_info' and description 'Get information about the authenticated user' indicate retrieval of user profile data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_user_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postman, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_user_info, this is the rule to start with:
get_user_info 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 Postman, apply this rule, and every get_user_info call is checked against it from then on.
Questions about get_user_info
Get information about the authenticated user. It is categorised as a Read tool in the Postman MCP Server, which means it retrieves data without modifying state.
Register the Postman MCP server in PolicyLayer and add a rule for get_user_info: 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 Postman. Nothing to install.
get_user_info 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_info 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_info. 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_info is provided by the Postman MCP server (delano/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postman, and thousands of servers like it.
This server
Across the catalogue