AI agents call contexto to retrieve information from Maestro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries accumulated project metadata and documentation. It has no capability to modify, execute operations, delete data, or commit financial actions.
From the tool's definition Tool name 'contexto' and description 'Retorna contexto acumulado do projeto' (Returns accumulated project context) — the verb 'Retorna' (Returns) indicates retrieval of existing data.
Attacks that exploit this kind of access
🧠Retorna contexto acumulado do projeto (ADRs, padrões, decisões, knowledge base). It is categorised as a Read tool in the Maestro MCP Server, which means it retrieves data without modifying state.
Register the Maestro MCP server in PolicyLayer and add a rule for contexto: 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.
contexto 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 contexto 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 contexto. 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.
contexto 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 →