AI agents use organize_files to create or update resources in Project Tessera — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Tessera environment.
Organizing files typically involves moving or renaming them (reversible Write operations), but the vague description leaves open the possibility of deletion or overwrite (Destructive). Given the ambiguity, Write is the most conservative applicable category above Read, while severity is medium because mis-organization of a workspace could cause data loss or confusion.
From the tool's definition "Organize files in the workspace" — the word 'organize' implies moving, renaming, or restructuring files.
Documented attack patterns abuse exactly the kind of access organize_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project Tessera, and nothing reaches the server without passing your rules. This is the rule we recommend for organize_files:
{
"version": "1",
"default": "deny",
"tools": {
"organize_files": {
"limits": [
{
"counter": "organize_files_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}organize_files 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.
Free to start. No card required.
Organize files in the workspace. It is categorised as a Write tool in the Project Tessera MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Project Tessera MCP server in PolicyLayer and add a rule for organize_files: 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 Project Tessera. Nothing to install.
organize_files 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 organize_files 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 organize_files. 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.
organize_files is provided by the Project Tessera MCP server (besslframework-stack/project-tessera). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project Tessera, 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.
43 Project Tessera tools catalogued and risk-classified — across an index of 43,000+ MCP servers.