Low Risk

lookup_address

Lookup Vietnamese administrative locations in Pancake POS via /geo/* endpoints. Polymorphic on ID format: OLD (e.g.

How to control lookup_address ↓

AI agents call lookup_address to retrieve information from Pancake Pos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Even though lookup_address only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access lookup_address gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Pancake Pos, and nothing reaches the server without passing your rules. This is the rule we recommend for lookup_address:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lookup_address": {}
  }
}

lookup_address is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Pancake Pos — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the lookup_address tool do? +

Lookup Vietnamese administrative locations in Pancake POS via /geo/* endpoints. Polymorphic on ID format: OLD (e.g. It is categorised as a Read tool in the Pancake Pos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_address? +

Register the Pancake Pos MCP server in PolicyLayer and add a rule for lookup_address: 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 Pancake Pos. Nothing to install.

What risk level is lookup_address? +

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

Can I rate-limit lookup_address? +

Yes. Add a rate_limit block to the lookup_address 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 lookup_address completely? +

Set action: deny in the PolicyLayer policy for lookup_address. 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 lookup_address? +

lookup_address is provided by the Pancake Pos MCP server (nguyennguyenit/pancake-pos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pancake Pos tool call.

Deterministic rules across all 24 Pancake Pos tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

24 Pancake Pos tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.