AI agents call wind_wsd to retrieve information from Wind MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The Wind MCP Server is explicitly designed for querying financial data. Tool name 'wind_wsd' follows the pattern of sibling tools (wind_wses, wind_wss) which appear to be data lookups. Without a description, confidence is moderated, but the server context indicates this retrieves financial time series or reference data rather than executing trades, modifying records, or causing destruction.
From the tool's definition Server is explicitly focused on 'query real-time financial data' with tools like 'search_windpy_doc', 'wind_tdays', and 'wind_wses'.
Documented attack patterns abuse exactly the kind of access wind_wsd gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wind MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wind_wsd:
{
"version": "1",
"default": "deny",
"tools": {
"wind_wsd": {}
}
}wind_wsd is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
wind_wsd. It is categorised as a Read tool in the Wind MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wind MCP Server MCP server in PolicyLayer and add a rule for wind_wsd: 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 Wind MCP Server. Nothing to install.
wind_wsd 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 wind_wsd 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 wind_wsd. 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.
wind_wsd is provided by the Wind MCP Server MCP server (abuttoncc/wind-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wind MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Wind MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.