AI agents use update_plan_week to create or update resources in MCPacer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCPacer environment.
This tool most likely updates training plan information for a specific week within the MCPacer coaching system. Updates to plan data are reversible Write operations. Severity is medium because misuse could alter a user's training regimen (affecting health/performance outcomes), but changes are typically reversible and lack the irreversibility of Destructive actions or financial impact.
From the tool's definition Tool name 'update_plan_week' indicates modification of plan data. Sibling tools include 'add_plan_comment', 'add_plan_run', and 'add_run_note', which are clearly Write operations modifying training plan content.
Documented attack patterns abuse exactly the kind of access update_plan_week gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCPacer, and nothing reaches the server without passing your rules. This is the rule we recommend for update_plan_week:
{
"version": "1",
"default": "deny",
"tools": {
"update_plan_week": {
"limits": [
{
"counter": "update_plan_week_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_plan_week stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
update_plan_week. It is categorised as a Write tool in the MCPacer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCPacer MCP server in PolicyLayer and add a rule for update_plan_week: 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 MCPacer. Nothing to install.
update_plan_week 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_plan_week 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_plan_week. 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_plan_week is provided by the MCPacer MCP server (wernerpe/mcpacer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCPacer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 MCPacer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.