AI agents call get_people to retrieve information from Basecamp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of people associated with a project. It performs no side effects, makes no changes to data, and poses minimal security risk. It is clearly a Read operation that queries existing project membership information.
From the tool's definition Tool name 'get_people' and description 'Get all people in a project' indicate a query/retrieval operation with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access get_people gives an agent:
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 get_people:
{
"version": "1",
"default": "deny",
"tools": {
"get_people": {}
}
}get_people 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.
Get all people in a project. It is categorised as a Read tool in the Basecamp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basecamp MCP Server MCP server in PolicyLayer and add a rule for get_people: 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.
get_people 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 get_people 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 get_people. 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.
get_people 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.
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.
Free to start. No card required.
56 Basecamp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.