vs_ecc_agent_shield · VibeServe MCP: Risk & Policy

WHAT IT DOES

What vs_ecc_agent_shield does on VibeServe

AI agents invoke vs_ecc_agent_shield to trigger actions in VibeServe. 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 vs_ecc_agent_shield needs a policy

This tool executes an external security scanning pipeline (AgentShield) rather than simply reading or retrieving pre-computed data. Execution of code analysis tools qualifies as Execute category.

From the tool's definition Tool description states 'Run ECC AgentShield security scan on provided code content' — the word 'Run' indicates execution of an external security scanning operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vs_ecc_agent_shield Rate-limited

vs_ecc_agent_shield 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": {
    "vs_ecc_agent_shield": {
      "limits": [
        {
          "counter": "vs_ecc_agent_shield_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 VibeServe, so you can run agents against it safely.

FAQ

Questions about vs_ecc_agent_shield

What does the vs_ecc_agent_shield tool do? +

Run ECC AgentShield security scan on provided code content. Checks for secrets, permission risks, hook injection, MCP risks, and config issues. It is categorised as a Execute tool in the VibeServe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vs_ecc_agent_shield? +

Register the VibeServe MCP server in PolicyLayer and add a rule for vs_ecc_agent_shield: 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 VibeServe. Nothing to install.

What risk level is vs_ecc_agent_shield? +

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

Can I rate-limit vs_ecc_agent_shield? +

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

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

vs_ecc_agent_shield is provided by the VibeServe MCP server (ncsound919/vibeserve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.