List comments on any Basecamp resource (message, todo, card, etc.). Works universally on all recording types.
AI agents call basecamp_list_comments 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.
Even though basecamp_list_comments only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
List comments on any Basecamp resource (message, todo, card, etc.). Works universally on all recording types. 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 basecamp_list_comments: 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.
basecamp_list_comments 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 basecamp_list_comments 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 basecamp_list_comments. 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.
basecamp_list_comments is provided by the Basecamp MCP Server MCP server (stefanoverna/basecamp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.