Update the content of the current week
AI agents use update_weekly_note to create or update resources in Sidvy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sidvy MCP Server environment.
This tool modifies note content for the current week, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, involve financial transactions, or perform reads only.
From the tool's definition Tool name 'update_weekly_note' and description 'Update the content of the current week' indicate modification of existing data. The verb 'update' combined with the note-taking context shows this creates or modifies data reversibly without deletion.
Attacks that exploit this kind of access
Update the content of the current week. It is categorised as a Write tool in the Sidvy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sidvy MCP Server MCP server in PolicyLayer and add a rule for update_weekly_note: 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 Sidvy MCP Server. Nothing to install.
update_weekly_note 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 update_weekly_note 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 update_weekly_note. 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.
update_weekly_note is provided by the Sidvy MCP Server MCP server (martinhjartmyr/sidvy-mcp). 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 →