Add work experience to your profile
AI agents use add_work_experience to create or update resources in Google Workspace MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace MCP Server environment.
This tool creates or modifies user profile information (work experience) in a reversible manner. It does not execute code, delete data irreversibly, move money, or perform external operations with unpredictable side effects. The blast radius is limited to the user's own profile data within the Workspace system. Classified as Write with low severity.
From the tool's definition Tool name is 'add_work_experience' and description states 'Add work experience to your profile', indicating creation of new profile data.
Attacks that exploit this kind of access
Add work experience to your profile. It is categorised as a Write tool in the Google Workspace MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Workspace MCP Server MCP server in PolicyLayer and add a rule for add_work_experience: 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 Google Workspace MCP Server. Nothing to install.
add_work_experience 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 add_work_experience 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 add_work_experience. 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.
add_work_experience is provided by the Google Workspace MCP Server MCP server (pbulbule13/google-mcp-server). 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 →