Return every PAF delivery point at a UK postcode, ordered by building number. Whitespace and case are normalised. Billable on a hit; valid postcodes with no delivery points return an empty list and are not charged.
AI agents call postio_postcode_lookup to retrieve information from Postio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval tool that queries a postcode database and returns matching addresses. It reads UK Royal Mail PAF (Postcode Address File) data without creating, modifying, or deleting records. The only side effect is billing on a successful hit, which is a normal business operation, not a security-relevant side effect.
From the tool's definition Tool returns delivery point data at a postcode; no modification, deletion, or execution of external commands. Description states 'Return every PAF delivery point' — a query operation with no side effects beyond billing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Return every PAF delivery point at a UK postcode, ordered by building number. Whitespace and case are normalised. Billable on a hit; valid postcodes with no delivery points return an empty list and are not charged. It is categorised as a Read tool in the Postio MCP Server, which means it retrieves data without modifying state.
Register the Postio MCP server in PolicyLayer and add a rule for postio_postcode_lookup: 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 Postio. Nothing to install.
postio_postcode_lookup 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 postio_postcode_lookup 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 postio_postcode_lookup. 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.
postio_postcode_lookup is provided by the Postio MCP server (postio-uk/postio-integrations). 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 →