hires_batch_remove_tags · 100Hires MCP Server MCP

WHAT IT DOES

What hires_batch_remove_tags does on 100Hires MCP Server

AI agents use hires_batch_remove_tags to create or update resources in 100Hires MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 100Hires MCP Server environment.

WHY IT NEEDS A POLICY

Why hires_batch_remove_tags needs a policy

Removing tags modifies candidate records by deleting metadata, but tags can likely be re-added, making this a reversible write operation rather than a destructive one. The bulk nature (up to 100 candidates) elevates severity to medium since an AI agent could accidentally strip tags from many records at once.

From the tool's definition Remove tags from multiple candidates in one request (max 100). Returns per-item results with partial success support.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hires_batch_remove_tags Rate-limited

hires_batch_remove_tags stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hires_batch_remove_tags": {
      "limits": [
        {
          "counter": "hires_batch_remove_tags_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches 100Hires MCP Server, so you can run agents against it safely.

FAQ

Questions about hires_batch_remove_tags

What does the hires_batch_remove_tags tool do? +

Remove tags from multiple candidates in one request (max 100). Returns per-item results with partial success support. It is categorised as a Write tool in the 100Hires MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on hires_batch_remove_tags? +

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

hires_batch_remove_tags is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hires_batch_remove_tags? +

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

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

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

// THE FULL RECORD

hires_batch_remove_tags is one line of 100Hires MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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