getUsersByUsernames
Retrieve multiple users profile information by their usernames.
This record as markdown: /tools/xdevplatform-xmcp/getusersbyusernames.md
What getUsersByUsernames does on Xdevplatform/xmcp
AI agents call getUsersByUsernames to retrieve information from Xdevplatform/xmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getUsersByUsernames is rated Low
This tool retrieves user profile information based on usernames. It performs a read-only query operation that returns existing data without modifying, deleting, or executing any actions. The retrieval of user profiles is a standard informational operation with minimal security risk—the severity is low because user profile data is typically meant to be discoverable and public-facing.
From the tool's definition Tool name 'getUsersByUsernames' and description 'Retrieve multiple users profile information by their usernames' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs getUsersByUsernames safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xdevplatform/xmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getUsersByUsernames, this is the rule to start with:
getUsersByUsernames 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 Xdevplatform/xmcp, apply this rule, and every getUsersByUsernames call is checked against it from then on.
Questions about getUsersByUsernames
Retrieve multiple users profile information by their usernames. It is categorised as a Read tool in the Xdevplatform/xmcp MCP Server, which means it retrieves data without modifying state.
Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for getUsersByUsernames: 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 Xdevplatform/xmcp. Nothing to install.
getUsersByUsernames 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 getUsersByUsernames 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 getUsersByUsernames. 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.
getUsersByUsernames is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Xdevplatform/x, and thousands of servers like it.
This server
Across the catalogue