用户确认操作成功后调用此工具,记录学习内容到向量数据库和MD文件。当用户说
AI agents use screen_learn_success to create or update resources in Screen Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Screen Agent environment.
This tool writes/stores learned operation success data to a vector database and markdown files after user confirmation. It creates/updates persistent records but does not execute commands, delete data, or involve financial transactions. The blast radius is low as it only records UI interaction learning data.
From the tool's definition 记录学习内容到向量数据库和MD文件 (records learning content to vector database and MD files)
Attacks that exploit this kind of access
用户确认操作成功后调用此工具,记录学习内容到向量数据库和MD文件。当用户说. It is categorised as a Write tool in the Screen Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Screen Agent MCP server in PolicyLayer and add a rule for screen_learn_success: 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 Screen Agent. Nothing to install.
screen_learn_success 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 screen_learn_success 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 screen_learn_success. 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.
screen_learn_success is provided by the Screen Agent MCP server (lqszhsp/screen-agent). 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 →