nova_feature · Maestro MCP: Risk & Policy

WHAT IT DOES

What nova_feature does on Maestro

AI agents invoke nova_feature to trigger actions in Maestro. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why nova_feature needs a policy

The tool description is minimal ('[Interno] Fluxo de nova feature' = '[Internal] New feature flow'), but given the server context — autonomous AI-assisted development with native pipelines, auto-correction, and code generation — this tool likely orchestrates a multi-step workflow that involves executing pipeline stages, writing/modifying code, and running automated processes.

From the tool's definition 'Fluxo de nova feature' (new feature flow) on an 'autonomous MCP server for AI-assisted development with auto-correction, inverted TDD, and native pipelines'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nova_feature Rate-limited

nova_feature stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nova_feature": {
      "limits": [
        {
          "counter": "nova_feature_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Maestro, so you can run agents against it safely.

FAQ

Questions about nova_feature

What does the nova_feature tool do? +

[Interno] Fluxo de nova feature. It is categorised as a Execute tool in the Maestro MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nova_feature? +

Register the Maestro MCP server in PolicyLayer and add a rule for nova_feature: 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.

What risk level is nova_feature? +

nova_feature is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit nova_feature? +

Yes. Add a rate_limit block to the nova_feature 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.

How do I block nova_feature completely? +

Set action: deny in the PolicyLayer policy for nova_feature. 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.

What MCP server provides nova_feature? +

nova_feature 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.