set_recruiting_candidate_profile
Create or update the Recruiting Candidate profile mixin on an existing person. candidate accepts person _id, email, or exact display name. Provide at least one of title, source, onsite, remote.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/set-recruiting-candidate-profile.md
What set_recruiting_candidate_profile does on Huly
AI agents use set_recruiting_candidate_profile 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.
Why set_recruiting_candidate_profile is rated Medium
The tool performs a create or update operation on a candidate profile, which is a reversible modification (Write category). It modifies recruiting data associated with a person record but does not delete, execute arbitrary code, or commit financial transactions.
From the tool's definition Tool description states 'Create or update the Recruiting Candidate profile mixin on an existing person,' which indicates reversible modification of data.
Attacks that exploit this kind of access
The rule that runs set_recruiting_candidate_profile 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 set_recruiting_candidate_profile, this is the rule to start with:
set_recruiting_candidate_profile 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every set_recruiting_candidate_profile call is checked against it from then on.
Questions about set_recruiting_candidate_profile
Create or update the Recruiting Candidate profile mixin on an existing person. candidate accepts person _id, email, or exact display name. Provide at least one of title, source, onsite, remote. 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.
Register the Huly MCP server in PolicyLayer and add a rule for set_recruiting_candidate_profile: 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.
set_recruiting_candidate_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_recruiting_candidate_profile 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 set_recruiting_candidate_profile. 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.
set_recruiting_candidate_profile 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.
More on Huly, and thousands of servers like it.
This server
Across the catalogue