AI agents call get_user to retrieve information from RoadBoard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing user information without modifying, deleting, or executing anything. It is a pure read operation that resolves user references to human-readable names, similar to a directory lookup. No destructive, financial, or executable operations are possible. Severity is low because user public profiles are non-sensitive data and misuse would have minimal blast radius.
From the tool's definition Tool description states 'Look up a user by ID and return their public profile' with fields id, username, displayName, email. The verb 'look up' and 'return' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Look up a user by ID and return their public profile: id, username, displayName, email. Use this to resolve raw userId/assigneeId references into human-readable names. It is categorised as a Read tool in the RoadBoard MCP Server, which means it retrieves data without modifying state.
Register the RoadBoard MCP server in PolicyLayer and add a rule for get_user: 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 RoadBoard. Nothing to install.
get_user 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 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. 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 is provided by the RoadBoard MCP server (maless88/roadboard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →