AI agents use update_my_profile to create or update resources in Hiring — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hiring environment.
The tool creates or modifies candidate profile information, which aligns with the Write category (reversible data modification). Severity is medium because misuse could corrupt a candidate's profile data or inject false information into hiring records, but the impact is limited to that individual's profile and does not involve deletion, financial transactions, or system-level operations.
From the tool's definition Tool name 'update_my_profile' and description 'Updates the candidate' indicate modification of candidate profile data. This is a write operation that modifies existing data reversibly.
Attacks that exploit this kind of access
Updates the candidate. It is categorised as a Write tool in the Hiring MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hiring MCP server in PolicyLayer and add a rule for update_my_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 Hiring. Nothing to install.
update_my_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 update_my_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 update_my_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.
update_my_profile is provided by the Hiring MCP server (meetvaghani12/hiring_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →