AI agents call get_forecast to retrieve information from PC-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves weather forecast data without modifying, executing operations, or triggering state changes. It is a straightforward read operation that returns information to the caller. The low severity reflects the minimal impact if misused - an agent could only retrieve forecast data, which poses no security risk.
From the tool's definition Tool name 'get_forecast' and description '获取当地天气预报' (get local weather forecast) indicate a data retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_forecast gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PC-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_forecast:
{
"version": "1",
"default": "deny",
"tools": {
"get_forecast": {}
}
}get_forecast 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.
获取当地天气预报. It is categorised as a Read tool in the PC-MCP MCP Server, which means it retrieves data without modifying state.
Register the PC- MCP server in PolicyLayer and add a rule for get_forecast: 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 PC-MCP. Nothing to install.
get_forecast 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 get_forecast 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 get_forecast. 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.
get_forecast is provided by the PC- MCP server (shijianzhong/mcp-server-for-pc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PC-MCP, 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.
6 PC-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.