manage_progress
查询成长摘要与事件,或以幂等方式记录学习事件、激活路径和更新任务。无公网数据库时仅作为临时演示状态。
This record as markdown: /tools/a02-career-navigation-mcp/manage-progress.md
What manage_progress does on A02 Career Navigation
AI agents use manage_progress to create or update resources in A02 Career Navigation, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your A02 Career Navigation environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | |
action | string | Yes | |
detail | string | — | |
status | string | — | |
path_id | string | — | |
task_id | string | — | |
user_id | string | Yes | |
skill_id | string | — | |
sentiment | string | — | |
event_type | string | — | |
occurred_at | string | — | |
resource_id | string | — |
Parameters from the server's own tool schema.
Why manage_progress is rated Medium
An AI agent can call manage_progress faster than any human can review: one bad instruction and it creates or modifies resources in A02 Career Navigation by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs manage_progress safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A02 Career Navigation, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_progress, this is the rule to start with:
manage_progress 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.
The button opens the PolicyLayer dashboard: create your workspace, connect A02 Career Navigation, apply this rule, and every manage_progress call is checked against it from then on.
Questions about manage_progress
查询成长摘要与事件,或以幂等方式记录学习事件、激活路径和更新任务。无公网数据库时仅作为临时演示状态。. It is categorised as a Write tool in the A02 Career Navigation MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
manage_progress accepts 12 parameters: limit, action, detail, status, path_id, task_id, user_id, skill_id, sentiment, event_type, occurred_at, resource_id. Required: action, user_id. The full parameter table on this page comes from the server's own tool schema.
Register the A02 Career Navigation MCP server in PolicyLayer and add a rule for manage_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 A02 Career Navigation. Nothing to install.
manage_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 manage_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 manage_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.
manage_progress is provided by the A02 Career Navigation MCP server (a02-career-navigation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A02 Career Navigation, and thousands of servers like it.
This server
Across the catalogue