AI agents use confirmar_classificacao to create or update resources in Maestro — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Maestro environment.
The tool appears to confirm/commit a reclassification decision following a PRD review, which is a write/state-change operation. It modifies some classification state within the system. Confidence is moderate because the description is very brief and internal ('[Interno]'), leaving the exact scope and blast radius unclear. Reclassification is likely reversible, placing it in Write rather than Destructive.
From the tool's definition 'Confirma reclassificação após PRD' — confirms a reclassification after a PRD (Product Requirements Document)
Attacks that exploit this kind of access
[Interno] Confirma reclassificação após PRD. It is categorised as a Write tool in the Maestro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Maestro MCP server in PolicyLayer and add a rule for confirmar_classificacao: 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 Maestro. Nothing to install.
confirmar_classificacao is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the confirmar_classificacao 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 confirmar_classificacao. 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.
confirmar_classificacao is provided by the Maestro MCP server (matheus-gama-deluna/maestro). 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 →