AI agents call yeepay_yop_gen_key_pair to retrieve information from Yop without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though yeepay_yop_gen_key_pair only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
根据密钥算法生成非对称加密的密钥对（公钥和私钥），并保存到本地路径. It is categorised as a Read tool in the Yop MCP Server, which means it retrieves data without modifying state.
Register the Yop MCP server in PolicyLayer and add a rule for yeepay_yop_gen_key_pair: 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 Yop. Nothing to install.
yeepay_yop_gen_key_pair 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 yeepay_yop_gen_key_pair 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 yeepay_yop_gen_key_pair. 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.
yeepay_yop_gen_key_pair is provided by the Yop MCP server (yop-platform/yop-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 →