MCP Path
Semantic Learning Consent-CMP
Semantic Learning Consent-CMP is a public reference for knowledge signals, learning candidates, and explainable orientation. It names the signal, policy, or flow an agent should understand before choosing a concrete tool.
Reference page for a documented MCP capability path.
- Type
- MCP path
- Family
- Learning & Knowledge Evolution
- Effect
- changes state
- Status
- Reference
- Path
- 11.7
Purpose
What this entry explains
What it does
This reference explains Semantic Learning Consent-CMP for knowledge signals, learning candidates, and explainable orientation. It is kept as a named reference so agents can cite the flow without inventing a tool name.
Use when
- Use this entry when an agent needs to carry out the bounded step "Semantic Learning Consent-CMP" for knowledge signals, learning candidates, and explainable orientation.
- Use it as a reference path when the catalog describes a capability but no single public tool name is explicit.
- Use it before chaining follow-up tools so the next step is based on current evidence.
Reference Use
How agents should cite and apply this area
Examples are maintained at family level and use only public tool names or reference paths already present in the catalog.
Semantic Learning Consent-CMP describes a gate for knowledge signals, learning candidates, and explainable orientation. The path shows which signal, gate, behavior, or boundary must be checked before choosing a concrete tool.
An agent cites this path when it needs Semantic Learning Consent-CMP as context for a decision, block, target check, or follow-up tool choice.
The public source does not name one callable tool for this path. The documentation therefore keeps it as a reference path and does not invent a callable name.
Relevant response signals: opportunityId. Safety axes: Browser state, Page interaction, User confirmation. The reference path alone is not permission to execute. Before acting, check current MCP discovery, visible target, scope, and the actual response.
Family example
A task touches data, identity, or permissions in knowledge signals, learning candidates, and explainable orientation that may be used only with clear purpose.
The agent starts with nova.learn_suggest, reads the current response or reference, and only then chooses the concrete next tool.
Sensitive values stay in current scope; they are not guessed, logged, or copied into other contexts.Contract
Inputs and important response fields
This page is a public reference. Agents and integrators should still read current MCP tool discovery before execution, because schemas can be gated by settings or version.
Inputs
No stable public input field is derived from the catalog source for this path. Read current MCP discovery before execution.
| Response field | Explanation |
|---|---|
opportunityId | Identifier or reference value. Do not guess it from memory; read it from the current response. |
Safety
Boundary before execution
Can change browser, page, or workflow state. The target and expected result must be clear before execution.
Treat stored knowledge as guidance only. Before any action, confirm the current page, target, scope, and visible evidence again.
For humans, this entry names the browser or workflow state in knowledge signals, learning candidates, and explainable orientation that may change, so the action can be reviewed before and after execution.
Safety Axes
How this path can affect work
Axes are stable catalog signals for humans, agents, and LLM discovery. One path can carry several axes.
browser_state_change
Changes tab, navigation, focus, claim, scroll position, window state, or browser environment.
Confirm the target context visibly before execution and verify that the expected browser state was reached afterwards.page_interaction
Clicks, types, selects, uploads, or interacts with visible page elements.
Execute only with a visible target, expected effect, and a follow-up result check.user_confirmation
Requires visible confirmation, target review, approval, or deliberate user control.
Do not proceed until the required confirmation is visible or unambiguous in the current context.