remove_person_from_project

THE RISK

Critical Risk

Why remove_person_from_project needs a policy

Revoking access removes permissions for users from a project. This is effectively irreversible in the sense that it immediately cuts off access, and restoring it requires deliberate re-invitation. The blast radius is high because an AI agent could accidentally remove legitimate users (including many at once) from a project, disrupting collaboration and potentially causing data access loss.

From the tool's definition Revoke access from one or more people for a project

Documented attack patterns abuse exactly the kind of access remove_person_from_project gives an agent:

POLICY

How to control remove_person_from_project

PolicyLayer is an MCP gateway — it sits between your AI agents and Basecamp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_person_from_project:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_person_from_project"
  ]
}

remove_person_from_project disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Basecamp MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Basecamp MCP Server tools

Destructive delete_webhook Delete a webhook Write reposition_todo Change the position/order of a todo within its list Write add_comment_to_card Add a comment to a card Write add_comment_to_document Add a comment to a document Write add_comment_to_message Add a comment/reply to a message Write add_comment_to_recording Add a comment to any Basecamp recording (universal comment tool) Write add_comment_to_todo Add a comment to a specific todo Write add_person_to_project Grant access to one or more people for a project

All 56 Basecamp MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Basecamp MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_person_from_project

What does the remove_person_from_project tool do? +

Revoke access from one or more people for a project. It is categorised as a Destructive tool in the Basecamp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_person_from_project? +

Register the Basecamp MCP Server MCP server in PolicyLayer and add a rule for remove_person_from_project: 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 Basecamp MCP Server. Nothing to install.

What risk level is remove_person_from_project? +

remove_person_from_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_person_from_project? +

Yes. Add a rate_limit block to the remove_person_from_project 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.

How do I block remove_person_from_project completely? +

Set action: deny in the PolicyLayer policy for remove_person_from_project. 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.

What MCP server provides remove_person_from_project? +

remove_person_from_project is provided by the Basecamp MCP Server MCP server (qusaiisaleem/basecamp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Basecamp MCP Server tool call.

Start from Basecamp MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →