filesystem_chown
Change ownership of a file or directory. Can optionally apply recursively.
This record as markdown: /tools/nasbridge/filesystem-chown.md
What filesystem_chown does on Nasbridge
AI agents invoke filesystem_chown to trigger actions in Nasbridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why filesystem_chown is rated High
Changing file/directory ownership is a privileged operation that modifies access control metadata on the filesystem. It can be applied recursively across entire directory trees, potentially granting or revoking access to sensitive data at scale.
From the tool's definition Change ownership of a file or directory. Can optionally apply recursively.
Attacks that exploit this kind of access
The rule that runs filesystem_chown 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_chown, this is the rule to start with:
filesystem_chown stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_chown call is checked against it from then on.
Questions about filesystem_chown
Change ownership of a file or directory. Can optionally apply recursively. It is categorised as a Execute tool in the Nasbridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nasbridge MCP server in PolicyLayer and add a rule for filesystem_chown: 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_chown is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the filesystem_chown 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_chown. 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_chown 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.
Across the catalogue