full_analysis · GPA Backend Test Analyst MCP: Risk & Policy

WHAT IT DOES

What full_analysis does on GPA Backend Test Analyst MCP

AI agents invoke full_analysis to trigger actions in GPA Backend Test Analyst MCP. 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 full_analysis needs a policy

This tool executes a full automated pipeline of operations (code analysis, test suite generation, architecture validation, documentation). It is not merely reading data; it actively runs processes and generates/writes artifacts. The most severe applicable category among its steps is Execute, as it runs code analysis pipelines and generates test suites.

From the tool's definition 'Pipeline completo: analisa código + gera testes + valida arquitetura + documenta' — triggers a multi-step pipeline combining analysis, test generation, architecture validation, and documentation generation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

full_analysis Rate-limited

full_analysis 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": {
    "full_analysis": {
      "limits": [
        {
          "counter": "full_analysis_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 GPA Backend Test Analyst MCP, so you can run agents against it safely.

FAQ

Questions about full_analysis

What does the full_analysis tool do? +

Pipeline completo: analisa código + gera testes + valida arquitetura + documenta. It is categorised as a Execute tool in the GPA Backend Test Analyst MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on full_analysis? +

Register the GPA Backend Test Analyst MCP server in PolicyLayer and add a rule for full_analysis: 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 GPA Backend Test Analyst MCP. Nothing to install.

What risk level is full_analysis? +

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

Can I rate-limit full_analysis? +

Yes. Add a rate_limit block to the full_analysis 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 full_analysis completely? +

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

full_analysis is provided by the GPA Backend Test Analyst MCP server (renanpires-tech/mcpautomation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.