wsl_catalog_stats
AI agents call wsl_catalog_stats to retrieve information from Pypi:wsl Envidat without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests it retrieves or computes statistics about the environmental data catalog, consistent with other Read category tools on this server. No write, execute, or destructive operations are implied. Confidence is moderate (0.7) because the description is empty, but the naming convention and server context strongly suggest catalog statistics retrieval with no side effects.
From the tool's definition Tool name 'wsl_catalog_stats' implies statistics retrieval from a catalog. Description is empty, but context shows this is part of a data query server (wsl-envidat-mcp) where all sibling tools are read-only data retrieval operations (get_*, list_*, search).
Attacks that exploit this kind of access
wsl_catalog_stats. It is categorised as a Read tool in the Pypi:wsl Envidat MCP Server, which means it retrieves data without modifying state.
Register the Pypi:wsl Envidat MCP server in PolicyLayer and add a rule for wsl_catalog_stats: 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 Pypi:wsl Envidat. Nothing to install.
wsl_catalog_stats 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 wsl_catalog_stats 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 wsl_catalog_stats. 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.
wsl_catalog_stats is provided by the Pypi:wsl Envidat MCP server (pypi:wsl-envidat-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 →