hires_get_user
Get a single user by ID within current tenant scope. Use for identity resolution in automation flows. The default_mail_account_id field can be used as from_account_id when sending emails.
This record as markdown: /tools/com-100hires-100hires/hires-get-user.md
What hires_get_user does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_get_user to retrieve information from 100Hires - AI ATS & Recruitment Software without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | User ID |
Parameters from the server's own tool schema.
Why hires_get_user is rated Low
This is a straightforward read operation that retrieves user data by ID within the current tenant scope. While it returns identity and email configuration information, it involves no creation, modification, deletion, execution, or financial operations. The capability to use returned data in other flows does not change the classification of this tool itself, which performs only data retrieval.
From the tool's definition Tool description states 'Get a single user by ID' which is a retrieval operation with no side effects. Returns identity information and mail account configuration.
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 - AI ATS & Recruitment Software, 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 - AI ATS & Recruitment Software, 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 default_mail_account_id field can be used as from_account_id when sending emails. It is categorised as a Read tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it retrieves data without modifying state.
hires_get_user accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the 100Hires - AI ATS & Recruitment Software 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 - AI ATS & Recruitment Software. 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 - AI ATS & Recruitment Software MCP server (https://mcp.100hires.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 100Hires - AI ATS & Recruitment Software, and thousands of servers like it.
Across the catalogue