release_files · Vigentic MCP: Risk & Policy

WHAT IT DOES

What release_files does on Vigentic MCP

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

This tool modifies file ownership metadata rather than the file contents themselves. It is reversible—ownership can be reclaimed or reassigned. The context (sibling tool 'claim_files' suggests a paired claim/release pattern) indicates this is a state management operation. It does not delete files (Destructive), execute code (Execute), or retrieve data (Read).

From the tool's definition Tool name 'release_files' combined with description 'Release explicit file ownership for an agent after handoff or completion' indicates modification of file ownership/metadata state. The term 'release' suggests relinquishing control over claimed resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

release_files Rate-limited

release_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": {
    "release_files": {
      "limits": [
        {
          "counter": "release_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 release_files

What does the release_files tool do? +

Release explicit file ownership for an agent after handoff or completion. 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 release_files? +

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

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

Can I rate-limit release_files? +

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

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

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