Check that the hCaptcha accessibility cookie is present and not
AI agents call validate_cookie to retrieve information from Suno Autopilot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a validation check on the presence of a cookie - a read-only operation that queries state without side effects. Even though it involves authentication/security infrastructure (hCaptcha), the tool itself only verifies existence, not modifying, executing, or deleting anything. The incomplete description ('and not') slightly reduces confidence but the intent remains clear as a read operation.
From the tool's definition Tool name 'validate_cookie' and description 'Check that the hCaptcha accessibility cookie is present and not' indicate a verification/checking operation with no modification of data or execution of external operations.
Attacks that exploit this kind of access
Check that the hCaptcha accessibility cookie is present and not. It is categorised as a Read tool in the Suno Autopilot MCP MCP Server, which means it retrieves data without modifying state.
Register the Suno Autopilot MCP server in PolicyLayer and add a rule for validate_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 Suno Autopilot MCP. Nothing to install.
validate_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 validate_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 validate_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.
validate_cookie is provided by the Suno Autopilot MCP server (voidreapercmxcix/suno-autopilot-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 →