Run admin temporary file cleanup.
AI agents invoke clean_admin_temp to trigger actions in Mealie MCP Server. 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.
This tool executes a system-level operation (admin cleanup) that performs side effects on the server's filesystem. While not permanently destructive in the sense of deleting user data, it irreversibly removes files and cannot be easily undone if the wrong temporary files are affected.
From the tool's definition 'Run admin temporary file cleanup' indicates execution of a cleanup/maintenance operation that modifies the filesystem state by deleting temporary files.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Run admin temporary file cleanup. It is categorised as a Execute tool in the Mealie MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for clean_admin_temp: 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 Mealie MCP Server. Nothing to install.
clean_admin_temp 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 clean_admin_temp 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 clean_admin_temp. 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.
clean_admin_temp is provided by the Mealie MCP Server MCP server (nikopol666/mealie-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →