setup_agents · Vigentic MCP: Risk & Policy

WHAT IT DOES

What setup_agents does on Vigentic MCP

AI agents use setup_agents to create or update resources in Vigentic MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vigentic MCP environment.

WHY IT NEEDS A POLICY

Why setup_agents needs a policy

This tool creates or modifies files (AGENTS.md and docs/agent-usage.md), which are reversible write operations. The changes can be undone through version control or manual editing. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions (would be Financial).

From the tool's definition Tool description states 'Create or update a repo-local Vigentic MCP contract in AGENTS.md and scaffold docs/agent-usage.md when it is missing' — the verbs 'create' and 'update' indicate write operations that modify or create files in the repository.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_agents Rate-limited

setup_agents stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setup_agents": {
      "limits": [
        {
          "counter": "setup_agents_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about setup_agents

What does the setup_agents tool do? +

Create or update a repo-local Vigentic MCP contract in AGENTS.md and scaffold docs/agent-usage.md when it is missing. It is categorised as a Write tool in the Vigentic MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setup_agents? +

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

What risk level is setup_agents? +

setup_agents is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setup_agents? +

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

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

setup_agents is provided by the Vigentic MCP server (munozu/vigentic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.