Get all steps (sub-tasks) for a card
AI agents call get_card_steps 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 queries and retrieves existing card step data from Basecamp without creating, modifying, deleting, or executing any actions. It is a straightforward read operation with minimal risk—the worst outcome would be unauthorized information disclosure of task subtasks within a project.
From the tool's definition Tool name 'get_card_steps' and description 'Get all steps (sub-tasks) for a card' indicate a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Get all steps (sub-tasks) for a card. 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_card_steps: 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_card_steps 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_card_steps 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_card_steps. 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_card_steps 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 →