addPlanActivity
Add a comment or activity entry to a plan.
This record as markdown: /tools/io-stablebaseline-sb/addplanactivity.md
What addPlanActivity does on Stable Baseline
AI agents use addPlanActivity to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
planId | string | Yes | |
comment | string | — | Comment text. |
metadata | object | — | Additional context. |
newValue | string | — | For field_change: new value. |
oldValue | string | — | For field_change: previous value. |
fieldName | string | — | For field_change: field name. |
activityType | string | — | Type: comment, agent_update, field_change. Default: comment. |
Parameters from the server's own tool schema.
Why addPlanActivity is rated Medium
The tool creates new activity entries or comments within a plan, which modifies the plan's state reversibly. This is a Write operation (create/modify data without destructive or side-effect execution). Severity is medium because unauthorized plan modifications could affect project tracking and team coordination, but the changes are auditable and reversible.
From the tool's definition Tool name includes 'add' and description states 'Add a comment or activity entry to a plan.' These are creation/modification operations that add reversible content.
Attacks that exploit this kind of access
The rule that runs addPlanActivity 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 addPlanActivity, this is the rule to start with:
addPlanActivity stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 addPlanActivity call is checked against it from then on.
Questions about addPlanActivity
Add a comment or activity entry to a plan. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
addPlanActivity accepts 7 parameters: planId, comment, metadata, newValue, oldValue, fieldName, activityType. 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 addPlanActivity: 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.
addPlanActivity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the addPlanActivity 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 addPlanActivity. 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.
addPlanActivity 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