Get coordinates for a location name or address using Amazon Location Service geo-places geocode API.
AI agents call geocode to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The geocode tool queries geographic data and returns coordinates without creating, modifying, deleting, or executing any operations. This is a straightforward read operation with minimal blast radius if misused by an AI agent — worst case would be exposing location data queries or consuming API quota, neither of which causes data loss or external harm.
From the tool's definition Tool description states 'Get coordinates for a location name or address' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get coordinates for a location name or address using Amazon Location Service geo-places geocode API. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for geocode: 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 AWS IoT SiteWise MCP Server. Nothing to install.
geocode 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 geocode 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 geocode. 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.
geocode is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.