AI agents call suggest_cleanup to retrieve information from Project Tessera without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or analyzes the state of the workspace memory and proposes cleanup recommendations. It does not actually perform deletions, modifications, or execute operations—it merely reads the workspace state and suggests actions. This is consistent with a Read category tool, as it has no side effects on the data itself.
From the tool's definition The tool 'suggest_cleanup' is described as suggesting cleanup actions. The word 'suggest' indicates it provides recommendations or proposals without executing changes.
Documented attack patterns abuse exactly the kind of access suggest_cleanup 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 suggest_cleanup:
{
"version": "1",
"default": "deny",
"tools": {
"suggest_cleanup": {}
}
}suggest_cleanup is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Suggest cleanup actions for the workspace. It is categorised as a Read tool in the Project Tessera MCP Server, which means it retrieves data without modifying state.
Register the Project Tessera MCP server in PolicyLayer and add a rule for suggest_cleanup: 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.
suggest_cleanup is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the suggest_cleanup 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 suggest_cleanup. 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.
suggest_cleanup 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.