remove_recruiting_candidate_skill

Detach a Recruiting skill from a candidate by skill title or tag ID. Idempotent when the skill is absent.

SERVERHuly SOURCE@firfi/huly-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/remove-recruiting-candidate-skill.md

WHAT IT DOES

What remove_recruiting_candidate_skill does on Huly

AI agents use remove_recruiting_candidate_skill to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.

RISK

Why remove_recruiting_candidate_skill is rated Medium

This tool removes (detaches) a skill from a candidate record. While it is a deletion of an association, it is idempotent and reversible (the skill can be re-attached), making it closer to a Write/modification operation than a truly irreversible Destructive action. The blast radius is medium as it modifies candidate profile data but can be undone.

From the tool's definition Detach a Recruiting skill from a candidate by skill title or tag ID. Idempotent when the skill is absent.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_recruiting_candidate_skill safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_recruiting_candidate_skill, this is the rule to start with:

remove_recruiting_candidate_skill Rate-limited

remove_recruiting_candidate_skill 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": {
    "remove_recruiting_candidate_skill": {
      "limits": [
        {
          "counter": "remove_recruiting_candidate_skill_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every remove_recruiting_candidate_skill call is checked against it from then on.

FAQ

Questions about remove_recruiting_candidate_skill

What does the remove_recruiting_candidate_skill tool do? +

Detach a Recruiting skill from a candidate by skill title or tag ID. Idempotent when the skill is absent. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remove_recruiting_candidate_skill? +

Register the Huly MCP server in PolicyLayer and add a rule for remove_recruiting_candidate_skill: 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 Huly. Nothing to install.

What risk level is remove_recruiting_candidate_skill? +

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

Can I rate-limit remove_recruiting_candidate_skill? +

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

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

remove_recruiting_candidate_skill is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →