AI agents call tor_check_anonymity to retrieve information from Tor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to check or verify anonymity status—a read-only query operation with no side effects. The empty description reduces confidence slightly, but the sibling tool 'tor_privacy_status' on the same server suggests this is part of a status/monitoring suite rather than an action tool. Low severity because reading privacy/anonymity status poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'tor_check_anonymity' suggests a status/diagnostic read operation. The server context describes 'tor_privacy_status' as a sibling tool, indicating this family performs queries rather than modifications.
Attacks that exploit this kind of access
tor_check_anonymity. It is categorised as a Read tool in the Tor MCP Server, which means it retrieves data without modifying state.
Register the Tor MCP server in PolicyLayer and add a rule for tor_check_anonymity: 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 Tor. Nothing to install.
tor_check_anonymity 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 tor_check_anonymity 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 tor_check_anonymity. 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.
tor_check_anonymity is provided by the Tor MCP server (rushikeshmore/tor-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 →