New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

filesystem_set_permissions

Set UNIX permissions on a file or directory. Can optionally apply recursively and strip existing ACLs.

SERVERTruenas SOURCEspranab/truenas-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/spranab-truenas-mcp/filesystem-set-permissions.md

What filesystem_set_permissions does on Truenas

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

Why filesystem_set_permissions is rated Medium

This tool modifies file and directory permissions, which are write operations that change system state. While permission changes are technically reversible (can be undone by resetting to previous values), the impact is significant—incorrect permission assignments could lock out legitimate users or expose sensitive data.

From the tool's definition Tool description states it 'Set[s] UNIX permissions on a file or directory' and can 'apply recursively and strip existing ACLs'. This modifies filesystem metadata and access control configurations, which are reversible but impactful changes.

Questions about filesystem_set_permissions

What does the filesystem_set_permissions tool do? +

Set UNIX permissions on a file or directory. Can optionally apply recursively and strip existing ACLs. It is categorised as a Write tool in the Truenas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on filesystem_set_permissions? +

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

What risk level is filesystem_set_permissions? +

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

Can I rate-limit filesystem_set_permissions? +

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

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

filesystem_set_permissions is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Truenas, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Truenas's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.