Update your personal details — name, email, phone, address. Only provide fields you want to change.
AI agents use update_personal_details to create or update resources in Shortlist MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shortlist MCP Server environment.
This tool creates or modifies user profile data (name, email, phone, address) without permanent deletion or financial impact. It is reversible—changes can be corrected or overwritten. It does not execute code or trigger external operations autonomously.
From the tool's definition Tool description states 'Update your personal details — name, email, phone, address', which are direct modifications to stored user profile data. The verb 'Update' and the context of profile management indicate reversible data modification.
Documented attack patterns abuse exactly the kind of access update_personal_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Shortlist MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_personal_details:
{
"version": "1",
"default": "deny",
"tools": {
"update_personal_details": {
"limits": [
{
"counter": "update_personal_details_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_personal_details 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.
Free to start. No card required.
Update your personal details — name, email, phone, address. Only provide fields you want to change. It is categorised as a Write tool in the Shortlist MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shortlist MCP Server MCP server in PolicyLayer and add a rule for update_personal_details: 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 Shortlist MCP Server. Nothing to install.
update_personal_details 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_personal_details 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_personal_details. 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_personal_details is provided by the Shortlist MCP Server MCP server (mls-tech-inc/shortlistjobs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Shortlist MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 Shortlist MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.