AI agents call get-postcode to retrieve information from Addressr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves postcode and locality information from an Australian address database. It performs a read-only lookup operation with no side effects, no code execution, no financial transactions, and no destructive actions. The low severity reflects minimal risk from misuse — an agent could retrieve address information but cannot modify, delete, or execute external operations.
From the tool's definition Tool description states 'Get full postcode details' and 'retrieve the postcode and associated localities' — these are query/retrieval operations with no modification or deletion of data.
Attacks that exploit this kind of access
Get full postcode details by URL. Follow the canonical link from search results to retrieve the postcode and associated localities. It is categorised as a Read tool in the Addressr MCP Server, which means it retrieves data without modifying state.
Register the Addressr MCP server in PolicyLayer and add a rule for get-postcode: 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 Addressr. Nothing to install.
get-postcode 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-postcode 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-postcode. 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-postcode is provided by the Addressr MCP server (mountain-pass/addressr-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 →