hires_get_user

Get a single user by ID within current tenant scope. Use for identity resolution in automation flows. The

SERVER100Hires MCP Server SOURCE100hires/mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about hires_get_user

What does the hires_get_user tool do? +

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.

How do I enforce a policy on hires_get_user? +

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.

What risk level is hires_get_user? +

hires_get_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hires_get_user? +

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.

How do I block hires_get_user completely? +

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.

What MCP server provides hires_get_user? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 100Hires MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.