Medium Risk

chmod_items

Change permissions mode for multiple specified files/directories (POSIX-style).

How to control chmod_items ↓

What chmod_items does on Filesystem

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

Medium Risk

Why chmod_items needs a policy

chmod operations change access control metadata on files and directories. While this is a modification operation (Write category), it is reversible—permissions can be re-chmod'd to restore prior state. It does not delete data or move money, so it does not qualify as Destructive or Financial.

From the tool's definition Tool is named 'chmod_items' and described as 'Change permissions mode for multiple specified files/directories (POSIX-style).' This modifies file/directory metadata (permissions) reversibly.

Documented attack patterns abuse exactly the kind of access chmod_items gives an agent:

How to control chmod_items

PolicyLayer is an MCP gateway — it sits between your AI agents and Filesystem, and nothing reaches the server without passing your rules. This is the rule we recommend for chmod_items:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "chmod_items": {
      "limits": [
        {
          "counter": "chmod_items_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Filesystem — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about chmod_items

What does the chmod_items tool do? +

Change permissions mode for multiple specified files/directories (POSIX-style). It is categorised as a Write tool in the Filesystem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on chmod_items? +

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

What risk level is chmod_items? +

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

Can I rate-limit chmod_items? +

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

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

chmod_items is provided by the Filesystem MCP server (sylphxai/filesystem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Filesystem tool call.

Start from Filesystem, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

13 Filesystem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.