claim_files · Vigentic MCP: Risk & Policy

WHAT IT DOES

What claim_files does on Vigentic MCP

AI agents use claim_files 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 claim_files needs a policy

This tool creates or modifies file ownership state (metadata), which is reversible and constitutes a write operation. It does not delete data (Destructive), execute arbitrary operations (Execute), trigger financial actions (Financial), or retrieve data without side effects (Read).

From the tool's definition Tool name 'claim_files' indicates ownership assignment for files. Description states it 'Claim[s] explicit file ownership for an agent before implementation begins.' This modifies metadata/state about file ownership within the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

claim_files Rate-limited

claim_files 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": {
    "claim_files": {
      "limits": [
        {
          "counter": "claim_files_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 claim_files

What does the claim_files tool do? +

Claim explicit file ownership for an agent before implementation begins. 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 claim_files? +

Register the Vigentic MCP server in PolicyLayer and add a rule for claim_files: 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 claim_files? +

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

Can I rate-limit claim_files? +

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

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

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