hires_get_user
Get a single user by ID within current tenant scope. Use for identity resolution in automation flows. The
This record as markdown: /tools/100hires-mcp-server/hires-get-user.md
What hires_get_user does on 100Hires MCP Server
AI agents call hires_get_user to retrieve information from 100Hires MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why hires_get_user is rated Low
This tool retrieves user information by ID within the current tenant scope. It performs a read-only lookup operation with no ability to modify, delete, or execute actions. The blast radius if misused is minimal — an AI agent could only view user details already accessible within the tenant, not alter hiring data or trigger external operations.
From the tool's definition Tool name is 'hires_get_user' and description states 'Get a single user by ID' — a retrieval operation with no side effects. The phrase 'Use for identity resolution in automation flows' confirms it queries/fetches data without modification.
Attacks that exploit this kind of access
The rule that runs hires_get_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 100Hires MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hires_get_user, this is the rule to start with:
hires_get_user 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 100Hires MCP Server, apply this rule, and every hires_get_user call is checked against it from then on.
Questions about hires_get_user
Get a single user by ID within current tenant scope. Use for identity resolution in automation flows. The. It is categorised as a Read tool in the 100Hires MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 100Hires MCP Server MCP server in PolicyLayer and add a rule for hires_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 100Hires MCP Server. Nothing to install.
hires_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 hires_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 hires_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.
hires_get_user is provided by the 100Hires MCP Server MCP server (100hires/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 100Hires MCP Server, and thousands of servers like it.
This server
Across the catalogue