Remove a project from favorites.
AI agents call favorite_project.remove to permanently remove resources in Freedcamp MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a project from favorites is a deletion action (removing a saved association), though it only affects a user preference/bookmark rather than actual project data. The blast radius is low since no real data is destroyed, but the action itself is irreversible in the sense that it deletes a favorites record.
From the tool's definition 'Remove a project from favorites' — the action removes/deletes a favorites entry
Attacks that exploit this kind of access
Remove a project from favorites. It is categorised as a Destructive tool in the Freedcamp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freedcamp MCP Server MCP server in PolicyLayer and add a rule for favorite_project.remove: 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 Freedcamp MCP Server. Nothing to install.
favorite_project.remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the favorite_project.remove 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 favorite_project.remove. 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.
favorite_project.remove is provided by the Freedcamp MCP Server MCP server (mahrukh-n8n/freedcampmcp). 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 →