AI agents use setup_inicial 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.
This tool writes/persists global configuration settings. While not destructive (changes are reversible), it modifies system state that affects subsequent operations. Severity is high because misconfigured global settings by an unreliable agent could degrade or break the entire development pipeline.
From the tool's definition Tool name 'setup_inicial' combined with description '[Interno] Salva configuração global' (Internal - Saves global configuration) indicates the tool creates or modifies configuration state persistently.
Attacks that exploit this kind of access
[Interno] Salva configuração global. Use. 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 setup_inicial: 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.
setup_inicial 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 setup_inicial 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 setup_inicial. 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.
setup_inicial 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 →