Retrieves active weather alerts for a specific US state (e.g. tornado watches, heat advisories).
AI agents call get-alerts to retrieve information from Subspace Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries weather alert data for a US state. It performs a read-only operation (retrieves) with no capability to create, modify, delete, or execute external operations. The data returned is informational and static. No reversible modifications, irreversible deletions, financial transactions, or code execution are involved.
From the tool's definition Tool name is 'get-alerts' and description states it 'Retrieves active weather alerts' — a query operation with no side effects or data modification.
Attacks that exploit this kind of access
Retrieves active weather alerts for a specific US state (e.g. tornado watches, heat advisories). It is categorised as a Read tool in the Subspace Api MCP Server, which means it retrieves data without modifying state.
Register the Subspace Api MCP server in PolicyLayer and add a rule for get-alerts: 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 Subspace Api. Nothing to install.
get-alerts 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-alerts 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-alerts. 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-alerts is provided by the Subspace Api MCP server (subtype-space/subspace-api). 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 →