AI agents call pje_consultar_processo_por_nome to retrieve information from Pje without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries judicial processes by party name in the Brazilian PJE system. It retrieves existing data with no side effects—no creation, modification, deletion, or execution of external operations. It fits the Read category: a search/query operation. Severity is low because querying public judicial records carries minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'pje_consultar_processo_por_nome' uses 'consultar' (consult/query) and description states 'Consulta processos' (consults/queries processes). The verb 'consultar' indicates retrieval without modification.
Attacks that exploit this kind of access
Consulta processos pelo nome da parte. It is categorised as a Read tool in the Pje MCP Server, which means it retrieves data without modifying state.
Register the Pje MCP server in PolicyLayer and add a rule for pje_consultar_processo_por_nome: 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 Pje. Nothing to install.
pje_consultar_processo_por_nome 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 pje_consultar_processo_por_nome 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 pje_consultar_processo_por_nome. 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.
pje_consultar_processo_por_nome is provided by the Pje MCP server (ma-serra/pje-mcp-server2). 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 →