Get ALL locations with pagination and filtering. Uses in-memory cache (5-min TTL) for fast queries on large datasets.\n\n
AI agents call pinmeto_get_locations to retrieve information from PinMeTo Location MCP 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 and lists locations from the PinMeTo service. It has no side effects—it does not create, modify, delete, or execute operations. The pagination and filtering are read-only query parameters.
From the tool's definition Tool retrieves location data via 'Get ALL locations with pagination and filtering' with no modification or deletion capabilities mentioned. The description explicitly frames this as a query operation with caching for performance.
Documented attack patterns abuse exactly the kind of access pinmeto_get_locations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PinMeTo Location MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for pinmeto_get_locations:
{
"version": "1",
"default": "deny",
"tools": {
"pinmeto_get_locations": {}
}
}pinmeto_get_locations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get ALL locations with pagination and filtering. Uses in-memory cache (5-min TTL) for fast queries on large datasets.\n\n. It is categorised as a Read tool in the PinMeTo Location MCP MCP Server, which means it retrieves data without modifying state.
Register the PinMeTo Location MCP server in PolicyLayer and add a rule for pinmeto_get_locations: 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 PinMeTo Location MCP. Nothing to install.
pinmeto_get_locations 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 pinmeto_get_locations 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 pinmeto_get_locations. 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.
pinmeto_get_locations is provided by the PinMeTo Location MCP server (pinmeto/pinmeto-location-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PinMeTo Location MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 PinMeTo Location MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.