New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

postcode_random

Get a random UK postcode with full location details.

SERVERUnClick SOURCE@unclick/mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about postcode_random

What does the postcode_random tool do? +

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.

How do I enforce a policy on postcode_random? +

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.

What risk level is postcode_random? +

postcode_random is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit postcode_random? +

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.

How do I block postcode_random completely? +

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.

What MCP server provides postcode_random? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UnClick's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.