Store how the user works - time management, focus, collaboration style
AI agents use add_work_style 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.
This tool creates or modifies user metadata (work style preferences) within the system. It is reversible and non-destructive - the data can be updated or removed without permanent loss. There are no side effects beyond storage, no code execution, no financial implications, and no irreversible data destruction.
From the tool's definition Tool name 'add_work_style' and description 'Store how the user works' indicate creation/modification of user preference data. The verb 'add' and 'store' confirm write operations on user profile information.
Attacks that exploit this kind of access
Store how the user works - time management, focus, collaboration style. 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 add_work_style: 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.
add_work_style 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_style 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_style. 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_style 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 →