Manage your user profile and preferences
AI agents use user-profile to create or update resources in IMCP - Insecure Model Context Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IMCP - Insecure Model Context Protocol environment.
The word 'manage' typically encompasses creating, reading, updating, and potentially deleting profile settings. The most severe applicable category for profile management (excluding destructive deletion, which is not explicitly mentioned) is Write. Given this is part of IMCP, a deliberately vulnerable framework, there is elevated risk of misuse such as privilege escalation or unauthorized profile modification.
From the tool's definition 'Manage your user profile and preferences' — 'manage' implies both read and write operations on profile data
Attacks that exploit this kind of access
Manage your user profile and preferences. It is categorised as a Write tool in the IMCP - Insecure Model Context Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the IMCP - Insecure Model Context Protocol MCP server in PolicyLayer and add a rule for user-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 IMCP - Insecure Model Context Protocol. Nothing to install.
user-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 user-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 user-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.
user-profile is provided by the IMCP - Insecure Model Context Protocol MCP server (nav33n25/imcp). 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 →