getPlan
Get full plan details including phases, items, and activity. Returns versionTimestamp — pass it to updatePlan for optimistic locking. Items include percent_complete for progress tracking.
This record as markdown: /tools/io-stablebaseline-sb/getplan.md
What getPlan does on Stable Baseline
AI agents call getPlan to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
planId | string | Yes |
Parameters from the server's own tool schema.
Why getPlan is rated Low
This tool retrieves and queries plan data without creating, modifying, executing code, or destructing data. The mention of versionTimestamp is passed to a separate 'updatePlan' tool, confirming this tool is read-only. No side effects or state mutations occur. Classified as Read with low severity due to minimal blast radius from accidental or malicious use—viewing plan details poses no operational risk.
From the tool's definition Tool name 'getPlan' and description states it 'Get[s] full plan details' and 'Returns versionTimestamp'. The description explicitly indicates retrieval operations with no modification capability ('Returns' data, mentions passing versionTimestamp to updatePlan…
Attacks that exploit this kind of access
The rule that runs getPlan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getPlan, this is the rule to start with:
getPlan is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every getPlan call is checked against it from then on.
Questions about getPlan
Get full plan details including phases, items, and activity. Returns versionTimestamp — pass it to updatePlan for optimistic locking. Items include percent_complete for progress tracking. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getPlan accepts 1 parameter: planId. Required: planId. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for getPlan: 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 Stable Baseline. Nothing to install.
getPlan 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 getPlan 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 getPlan. 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.
getPlan is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue