custom_name
AI agents call custom_name to retrieve information from Australian Postcodes MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, confidence is reduced. However, the server context strongly indicates Read operations (search, validate, retrieve). The tool name 'custom_name' is generic and could theoretically be anything, but given the server's stated function and the absence of any destructive language, the most likely classification is Read with low severity—retrieving location data poses minimal risk if misused by an AI…
From the tool's definition Tool name 'custom_name' is non-descriptive; description is empty. Based on the server's documented purpose—'search, validate, and retrieve Australian postcode and suburb data'—sibling tools like 'autocomplete', 'fuzzy_match_suburb', 'get_info', and…
Attacks that exploit this kind of access
custom_name. It is categorised as a Read tool in the Australian Postcodes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Australian Postcodes MCP Server MCP server in PolicyLayer and add a rule for custom_name: 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 Australian Postcodes MCP Server. Nothing to install.
custom_name 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 custom_name 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 custom_name. 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.
custom_name is provided by the Australian Postcodes MCP Server MCP server (jezweb/australian-postcodes-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 →