Find nodes in a specific geographic location or region (city, state, region, etc.)
AI agents call get_nodes_by_location to retrieve information from Sage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only lookup of node information filtered by geographic parameters. It has no side effects, does not execute operations, and does not modify or delete data. The blast radius of misuse is minimal — an attacker could only discover which nodes exist in certain locations, which is informational. This aligns with the 'Read' category for retrieval/query tools.
From the tool's definition Tool description states 'Find nodes in a specific geographic location or region' — this is a query operation that retrieves information about node locations without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Find nodes in a specific geographic location or region (city, state, region, etc.). It is categorised as a Read tool in the Sage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP Server MCP server in PolicyLayer and add a rule for get_nodes_by_location: 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 Sage MCP Server. Nothing to install.
get_nodes_by_location 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_nodes_by_location 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_nodes_by_location. 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_nodes_by_location is provided by the Sage MCP Server MCP server (waggle-sensor/sage-mcp). 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 →