hires_list_statuses

List job status labels (draft, published, on_hold, closed, archived). Cache to validate job status updates.

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-list-statuses.md

WHAT IT DOES

What hires_list_statuses does on 100Hires MCP Server

AI agents call hires_list_statuses 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.

RISK

Why hires_list_statuses is rated Low

This tool retrieves metadata about job status options without creating, modifying, or deleting any data. It is a simple lookup/validation cache for job statuses. Risk of misuse by an AI agent is minimal—the worst outcome would be reading stale or incorrect status information, not operational harm.

From the tool's definition Tool description states 'List job status labels' — a retrieval operation with no side effects. The enumerated statuses (draft, published, on_hold, closed, archived) are read-only reference data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hires_list_statuses 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_list_statuses, this is the rule to start with:

hires_list_statuses Allowed

hires_list_statuses is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hires_list_statuses": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 100Hires MCP Server, apply this rule, and every hires_list_statuses call is checked against it from then on.

FAQ

Questions about hires_list_statuses

What does the hires_list_statuses tool do? +

List job status labels (draft, published, on_hold, closed, archived). Cache to validate job status updates. 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_list_statuses? +

Register the 100Hires MCP Server MCP server in PolicyLayer and add a rule for hires_list_statuses: 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_list_statuses? +

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

Can I rate-limit hires_list_statuses? +

Yes. Add a rate_limit block to the hires_list_statuses 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_list_statuses completely? +

Set action: deny in the PolicyLayer policy for hires_list_statuses. 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_list_statuses? +

hires_list_statuses 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.

KEEP EXPLORING

More on 100Hires MCP Server, and thousands of servers like it.

This server

All 130 100Hires MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →