AI agents call onpe_sync_domestic_catalog 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.
Although 'sync' implies a write operation locally, the tool's purpose is to retrieve and cache reference/catalog data from ONPE's electoral system. This is a data population operation that maintains read-only reference information (administrative geography) needed for other queries. It has no destructive effects, creates no user-facing modifications, executes no arbitrary code, and commits no financial transactions.
From the tool's definition Tool name 'onpe_sync_domestic_catalog' and description 'Sincroniza el catálogo completo de ubigeos domésticos (departamentos/provincias/distritos)' indicates synchronization of a geographic/administrative catalog.
Attacks that exploit this kind of access
Sincroniza el catálogo completo de ubigeos domésticos (departamentos/provincias/distritos). 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_sync_domestic_catalog: 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_sync_domestic_catalog 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_sync_domestic_catalog 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_sync_domestic_catalog. 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_sync_domestic_catalog 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 →