AI agents call onpe_sv_resultados_geo 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.
The tool name and server context indicate this retrieves or queries geographic electoral results (resultados_geo). No modification, deletion, execution, or financial operations are implied. The '_resultados' suffix and '_geo' spatial reference align with data retrieval patterns seen in sibling tools. Confidence is moderate because the description is empty and does not explicitly confirm read-only semantics.
From the tool's definition Tool name 'onpe_sv_resultados_geo' suggests retrieval of electoral results with geographic/spatial data. Sibling tools (db_query, db_search, onpe_2021_export_mesas, onpe_2021_export_votos) are all read-only data retrieval operations.
Attacks that exploit this kind of access
onpe_sv_resultados_geo. 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_sv_resultados_geo: 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_sv_resultados_geo 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_sv_resultados_geo 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_sv_resultados_geo. 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_sv_resultados_geo 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 →