AI agents call state_cookies to retrieve information from Ruyipage without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention, this tool retrieves browser cookie information without modifying or executing operations. The 'state_' prefix indicates inspection/query of state rather than mutation.
From the tool's definition Tool name 'state_cookies' strongly suggests retrieval of cookie state/data from the browser. Tool description is empty, limiting definitiveness.
Attacks that exploit this kind of access
state_cookies. It is categorised as a Read tool in the Ruyipage MCP Server, which means it retrieves data without modifying state.
Register the Ruyipage MCP server in PolicyLayer and add a rule for state_cookies: 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 Ruyipage. Nothing to install.
state_cookies 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 state_cookies 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 state_cookies. 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.
state_cookies is provided by the Ruyipage MCP server (neverl805/ruyipage_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 →