Set a personal profile field (name, email, phone, linkedin, github, summary, etc.)
AI agents use set_profile to create or update resources in Enhanced MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced MCP Server environment.
The tool performs reversible modification of personal profile data. While it creates or updates fields, these changes can be undone by setting different values. It does not execute code, delete data permanently, or involve financial operations.
From the tool's definition Tool description states 'Set a personal profile field' which modifies user profile data fields (name, email, phone, linkedin, github, summary, etc.). This is a create/update operation on user profile information.
Attacks that exploit this kind of access
Set a personal profile field (name, email, phone, linkedin, github, summary, etc.). It is categorised as a Write tool in the Enhanced MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced MCP Server MCP server in PolicyLayer and add a rule for set_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 Enhanced MCP Server. Nothing to install.
set_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_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_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_profile is provided by the Enhanced MCP Server MCP server (pbulbule13/mcpwithgoogle). 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 →