AI agents call gerar_relatorio as a supporting operation in Maestro workflows.
The description provides no actionable information about what this tool does. The name 'gerar_relatorio' translates from Portuguese as 'generate report', which suggests a Read-like operation (producing/reading a report), but without any description confirming this, confidence is very low. Defaulting to Other with low severity given the ambiguity.
From the tool's definition Tool description is '[Interno] Use' — uninformative and essentially empty.
Attacks that exploit this kind of access
[Interno] Use. It is categorised as a Other tool in the Maestro MCP Server, which means it performs auxiliary operations.
Register the Maestro MCP server in PolicyLayer and add a rule for gerar_relatorio: 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.
gerar_relatorio is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gerar_relatorio 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 gerar_relatorio. 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.
gerar_relatorio 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 →