AI agents call purroxy_status to retrieve information from Purroxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the state of a local service without retrieving sensitive data, modifying any configuration, executing code, or performing destructive operations. It is a simple health check that returns boolean or status information. The low severity reflects minimal blast radius if misused - an attacker could only learn whether the app is running, not gain unauthorized access or cause harm.
From the tool's definition Tool description states it 'Check[s] whether the Purroxy desktop app is running and reachable on the local machine' - a pure status query with no side effects or state modifications.
Attacks that exploit this kind of access
Check whether the Purroxy desktop app is running and reachable on the local machine. It is categorised as a Read tool in the Purroxy MCP Server, which means it retrieves data without modifying state.
Register the Purroxy MCP server in PolicyLayer and add a rule for purroxy_status: 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 Purroxy. Nothing to install.
purroxy_status 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 purroxy_status 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 purroxy_status. 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.
purroxy_status is provided by the Purroxy MCP server (kuvopllc/purroxy2). 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 →