Get schedules from a project.
AI agents call get_schedules 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 schedule data from a Basecamp project without creating, modifying, deleting, or executing any operations. It is a read-only query operation with minimal risk; the blast radius of misuse would be limited to exposure of schedule information already accessible to the authenticated user.
From the tool's definition Tool name 'get_schedules' and description 'Get schedules from a project' indicate a retrieval operation with no modification or execution of external actions.
Attacks that exploit this kind of access
Get schedules from 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_schedules: 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_schedules 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_schedules 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_schedules. 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_schedules is provided by the Basecamp MCP Server MCP server (kbhalerao/basecamp-mcp). 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 →