List workflows learned from capture sessions.
AI agents call list_learned_workflows to retrieve information from Qontinui Web MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing workflow data from capture sessions without modifying, creating, deleting, or executing anything. It is purely informational, making it a Read category tool with low severity since it only exposes workflow metadata without the ability to modify or execute them.
From the tool's definition Tool name 'list_learned_workflows' and description 'List workflows learned from capture sessions' indicate a retrieval operation with no side effects. The verb 'list' is explicitly a Read operation as defined in the classification rules.
Attacks that exploit this kind of access
List workflows learned from capture sessions. It is categorised as a Read tool in the Qontinui Web MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qontinui Web MCP Server MCP server in PolicyLayer and add a rule for list_learned_workflows: 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 Qontinui Web MCP Server. Nothing to install.
list_learned_workflows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_learned_workflows 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 list_learned_workflows. 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.
list_learned_workflows is provided by the Qontinui Web MCP Server MCP server (qontinui/qontinui-web-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 →