AI agents use set_energy_profile to create or update resources in Gcal — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gcal environment.
This tool modifies user-stored configuration data (energy profile preferences) but does not delete data, execute code, move money, or cause irreversible changes. It is a reversible write operation that stores scheduling preferences. Severity is low because misuse would only affect the user's own calendar optimization logic, with no blast radius beyond personal scheduling suggestions.
From the tool's definition The tool 'saves' a user's energy profile data (create/modify operation). The description states 'Save your typical daily energy windows,' which is a write operation that creates or updates user preference data.
Attacks that exploit this kind of access
Save your typical daily energy windows. Claude uses this to match high-energy tasks to your peak hours. Example: high energy 9-11 AM, medium 11 AM-1 PM, low 2-4 PM. It is categorised as a Write tool in the Gcal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gcal MCP server in PolicyLayer and add a rule for set_energy_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 Gcal. Nothing to install.
set_energy_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_energy_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_energy_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_energy_profile is provided by the Gcal MCP server (kwikkid/gcalcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
set_energy_profile is one line of Gcal's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →