AI agents use everhour_update_time_record to create or update resources in Everhour — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Everhour environment.
An AI agent can call everhour_update_time_record faster than any human can review — one bad instruction and it creates or modifies resources in Everhour by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Update an existing time record in Everhour. Time can be specified in seconds or human-readable format. It is categorised as a Write tool in the Everhour MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Everhour MCP server in PolicyLayer and add a rule for everhour_update_time_record: 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 Everhour. Nothing to install.
everhour_update_time_record 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 everhour_update_time_record 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 everhour_update_time_record. 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.
everhour_update_time_record is provided by the Everhour MCP server (stefanskiasan/everhour-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.