Search across Basecamp projects, todos, and messages
AI agents call search_basecamp 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 performs a query/search operation across existing Basecamp data. It retrieves or queries information without creating, modifying, deleting, or executing external operations. No side effects are caused by the search itself. This is a straightforward Read category tool with low severity because misuse would only expose information the user already has access to in their Basecamp account.
From the tool's definition Tool name 'search_basecamp' and description 'Search across Basecamp projects, todos, and messages' indicate data retrieval with no modification or deletion capabilities.
Attacks that exploit this kind of access
Search across Basecamp projects, todos, and messages. 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 search_basecamp: 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.
search_basecamp 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 search_basecamp 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 search_basecamp. 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.
search_basecamp is provided by the Basecamp MCP Server MCP server (jhliberty/basecamp-mcp-server). 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 →