getUsersByUsername
Retrieve a user profile information by their username.
This record as markdown: /tools/xdevplatform-xmcp/getusersbyusername.md
What getUsersByUsername does on Xdevplatform/xmcp
AI agents call getUsersByUsername 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 getUsersByUsername is rated Low
This tool performs a straightforward data retrieval operation. It queries user profile information by username, which is a read-only action. There is no indication of data modification, deletion, code execution, or financial operations. The severity is low because username-based profile lookups are typically non-sensitive queries in most systems, though actual risk depends on what profile information is exposed.
From the tool's definition Tool name 'getUsersByUsername' and description 'Retrieve a user profile information by their username' indicate a query operation that retrieves existing data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs getUsersByUsername 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 getUsersByUsername, this is the rule to start with:
getUsersByUsername 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 getUsersByUsername call is checked against it from then on.
Questions about getUsersByUsername
Retrieve a user profile information by their username. 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 getUsersByUsername: 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.
getUsersByUsername 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 getUsersByUsername 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 getUsersByUsername. 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.
getUsersByUsername 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