AI agents call check_douyin_cookie to retrieve information from Dy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and validates cookie status—it performs a credential verification check with no side effects, data modification, or external operations triggered. While it deals with sensitive authentication data, the operation itself is a read-only validation. Severity is low because misuse would be limited to checking validity rather than accessing restricted resources or performing unauthorized actions.
From the tool's definition Tool name: check_douyin_cookie. Description: '检查账号 cookie 是否可用' (Check whether account cookie is available). The function validates/checks the status of authentication credentials without modifying or executing actions.
Documented attack patterns abuse exactly the kind of access check_douyin_cookie gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dy, and nothing reaches the server without passing your rules. This is the rule we recommend for check_douyin_cookie:
{
"version": "1",
"default": "deny",
"tools": {
"check_douyin_cookie": {}
}
}check_douyin_cookie is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
检查账号 cookie 是否可用. It is categorised as a Read tool in the Dy MCP Server, which means it retrieves data without modifying state.
Register the Dy MCP server in PolicyLayer and add a rule for check_douyin_cookie: 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 Dy. Nothing to install.
check_douyin_cookie 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 check_douyin_cookie 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 check_douyin_cookie. 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.
check_douyin_cookie is provided by the Dy MCP server (vipcong816/dy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Dy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.