Returns any active alerts posted by WMATA (metro). Can sometimes be empty.
AI agents call get-wmata-incidents 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 real-time metro incident and alert information from WMATA without modifying, executing, or deleting any data. It is a straightforward read operation with minimal blast radius—misuse would only result in unnecessary API calls or redundant data fetches, not damage or unintended state changes.
From the tool's definition Tool name is 'get-wmata-incidents' and description states 'Returns any active alerts posted by WMATA'. The verb 'Returns' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Returns any active alerts posted by WMATA (metro). Can sometimes be empty. 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-wmata-incidents: 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-wmata-incidents 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-wmata-incidents 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-wmata-incidents. 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-wmata-incidents 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 →