update_progress
AI agents use update_progress to create or update resources in Learning Coach MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Learning Coach MCP Server environment.
This tool modifies stored learning progress records, making it a Write operation. It creates or updates reversible state (progress tracking data). Severity is medium because misuse could corrupt a user's learning records, but the blast radius is limited to personal learning data without direct financial or destructive consequences.
From the tool's definition Tool name 'update_progress' indicates modification of tracked learning progress data. Description is empty, limiting specificity, but context from server description shows the tool tracks learning progress as persistent state.
Attacks that exploit this kind of access
update_progress. It is categorised as a Write tool in the Learning Coach MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Learning Coach MCP Server MCP server in PolicyLayer and add a rule for update_progress: 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 Learning Coach MCP Server. Nothing to install.
update_progress 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_progress 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_progress. 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_progress is provided by the Learning Coach MCP Server MCP server (pevansh/learning_coach_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 →