getPlanPhase
Get a plan phase by ID with full details. Returns versionTimestamp — pass it to updatePlanPhase for optimistic locking.
This record as markdown: /tools/io-stablebaseline-sb/getplanphase.md
What getPlanPhase does on Stable Baseline
AI agents call getPlanPhase 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 |
|---|---|---|---|
phaseId | string | Yes |
Parameters from the server's own tool schema.
Why getPlanPhase is rated Low
This tool retrieves data (a plan phase) by ID and returns information including a versionTimestamp for use in subsequent operations. It performs a query without modifying, deleting, or executing code. The mention of versionTimestamp is a detail for optimistic locking in write operations (updatePlanPhase), not a side effect of this tool itself.
From the tool's definition Tool name 'getPlanPhase' and description 'Get a plan phase by ID with full details' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs getPlanPhase 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 getPlanPhase, this is the rule to start with:
getPlanPhase 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 getPlanPhase call is checked against it from then on.
Questions about getPlanPhase
Get a plan phase by ID with full details. Returns versionTimestamp — pass it to updatePlanPhase for optimistic locking. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getPlanPhase accepts 1 parameter: phaseId. Required: phaseId. 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 getPlanPhase: 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.
getPlanPhase 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 getPlanPhase 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 getPlanPhase. 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.
getPlanPhase 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