AI agents call onpe_mesa_geo_lookup to retrieve information from Onpe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a lightweight query that retrieves and returns geolocation and status data associated with a polling station identifier. There are no side effects, no data modification, no code execution, and no destructive operations. The explicit exclusion of vote data ('sin votos') further confirms it is a simple read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'onpe_mesa_geo_lookup' and description 'Lookup ligero: dada una mesa, devuelve SOLO geo + estado (sin votos)' indicate a read-only lookup that retrieves geographic location and status information for a polling station (mesa), explicitly excluding…
Attacks that exploit this kind of access
Lookup ligero: dada una mesa, devuelve SOLO geo + estado (sin votos). It is categorised as a Read tool in the Onpe MCP Server, which means it retrieves data without modifying state.
Register the Onpe MCP server in PolicyLayer and add a rule for onpe_mesa_geo_lookup: 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 Onpe. Nothing to install.
onpe_mesa_geo_lookup 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 onpe_mesa_geo_lookup 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 onpe_mesa_geo_lookup. 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.
onpe_mesa_geo_lookup is provided by the Onpe MCP server (oscarzamora/onpe-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 →