This record as markdown: /tools/com-files-python-mcp/create-permission.md
What Create_Permission does on Files Com
AI agents use Create_Permission to create or update resources in Files Com, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Files Com environment.
Why Create_Permission is rated Medium
This tool creates a new permission entity, which is a reversible modification to access control state. While permissions are critical to security, creation itself is Write-category (reversible via deletion/modification), not Destructive.
From the tool's definition Tool name 'Create_Permission' and description 'Create Permission' indicate creation of a new permission record. Sibling tools include 'Delete_Bundle', 'Create_Bundle', 'Create_User', and 'Create_Folder', all of which are Write operations.
Attacks that exploit this kind of access
The rule that runs Create_Permission safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Create_Permission, this is the rule to start with:
Create_Permission 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 Files Com, apply this rule, and every Create_Permission call is checked against it from then on.
Questions about Create_Permission
Create_Permission is a write tool on the Files Com MCP server. It is categorised as a Write tool in the Files Com MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Files Com MCP server in PolicyLayer and add a rule for Create_Permission: 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 Files Com. Nothing to install.
Create_Permission 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 Create_Permission 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 Create_Permission. 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.
Create_Permission is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Files Com, and thousands of servers like it.
This server
Across the catalogue