postcode_random
Get a random UK postcode with full location details.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/postcode-random.md
What postcode_random does on UnClick
AI agents call postcode_random to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why postcode_random is rated Low
This tool simply queries and returns a random UK postcode along with associated location details. It performs a read-only operation on what is typically public geographic reference data. There is no data modification, code execution, deletion, or financial impact. The low severity reflects minimal risk even if misused by an AI agent, as the worst outcome would be receiving unwanted postcode data.
From the tool's definition Tool description states 'Get a random UK postcode' — a retrieval operation that returns public location data with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs postcode_random safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For postcode_random, this is the rule to start with:
postcode_random is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every postcode_random call is checked against it from then on.
Questions about postcode_random
Get a random UK postcode with full location details. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for postcode_random: 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 UnClick. Nothing to install.
postcode_random 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 postcode_random 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 postcode_random. 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.
postcode_random is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue