filesystem_set_acl
Set the Access Control List (ACL) for a file or directory. This is a powerful operation — the
This record as markdown: /tools/nasbridge/filesystem-set-acl.md
What filesystem_set_acl does on Nasbridge
AI agents use filesystem_set_acl to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge environment.
Why filesystem_set_acl is rated Medium
The tool modifies access control permissions on filesystem objects, which is a reversible write operation with potentially broad security implications. While ACLs can be changed back, improper modification could lock users out of critical files or expose sensitive data. The description explicitly characterizes it as 'powerful,' indicating significant blast radius.
From the tool's definition 'Set the Access Control List (ACL) for a file or directory. This is a powerful operation'
Attacks that exploit this kind of access
The rule that runs filesystem_set_acl safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For filesystem_set_acl, this is the rule to start with:
filesystem_set_acl 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every filesystem_set_acl call is checked against it from then on.
Questions about filesystem_set_acl
Set the Access Control List (ACL) for a file or directory. This is a powerful operation — the. It is categorised as a Write tool in the Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nasbridge MCP server in PolicyLayer and add a rule for filesystem_set_acl: 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 Nasbridge. Nothing to install.
filesystem_set_acl is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the filesystem_set_acl 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.
Set action: deny in the PolicyLayer policy for filesystem_set_acl. 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.
filesystem_set_acl is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue