AI agents call get_weather to retrieve information from MCP-Guide without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves weather data for a specified location without modifying, deleting, or executing any operations. It is a simple read-only query that returns information. The severity is low because misuse would only result in retrieving incorrect or irrelevant weather data, with no risk to systems, data integrity, or financial impact.
From the tool's definition Tool name 'get_weather' and description 'Get weather for a location' indicate a data retrieval operation with no side effects. The verb 'get' and the nature of weather information (read-only query result) confirm this is a retrieval action.
Documented attack patterns abuse exactly the kind of access get_weather gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Guide, and nothing reaches the server without passing your rules. This is the rule we recommend for get_weather:
{
"version": "1",
"default": "deny",
"tools": {
"get_weather": {}
}
}get_weather 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.
Get weather for a location. It is categorised as a Read tool in the MCP-Guide MCP Server, which means it retrieves data without modifying state.
Register the MCP-Guide MCP server in PolicyLayer and add a rule for get_weather: 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 MCP-Guide. Nothing to install.
get_weather 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_weather 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_weather. 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_weather is provided by the MCP-Guide MCP server (qpd-v/mcp-guide). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 MCP-Guide tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 MCP-Guide tools catalogued and risk-classified — across an index of 42,500+ MCP servers.