wsl_list_organizations
AI agents call wsl_list_organizations 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.
This tool retrieves or lists organizations from the WSL/EnviDat database with no modification capability. It has no side effects and fits the pattern of Read category tools (search, list, get, fetch) on this environmental data server. Low severity because listing organizational metadata poses minimal risk even if exposed to an AI agent.
From the tool's definition Tool name 'wsl_list_organizations' combined with sibling tools that are all data retrieval operations (search, get, list, catalog_stats). The 'list' verb indicates enumeration of data. No description provided, but context strongly suggests a query operation.
Attacks that exploit this kind of access
wsl_list_organizations. 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_list_organizations: 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_list_organizations 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_list_organizations 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_list_organizations. 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_list_organizations 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 →