post_project_update
Append a dated narrative status update (Linear-style) to the project
This record as markdown: /tools/ai-featureboard-featureboard/post-project-update.md
What post_project_update does on FeatureBoard
AI agents use post_project_update to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why post_project_update is rated Medium
This tool creates and appends new status update records to a project. The operation is reversible (updates can be deleted or replaced), so it is Write rather than Destructive.
From the tool's definition Tool description states it 'Append[s] a dated narrative status update' to the project, which is a create/modify operation that adds new content reversibly.
Attacks that exploit this kind of access
The rule that runs post_project_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For post_project_update, this is the rule to start with:
post_project_update 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 FeatureBoard, apply this rule, and every post_project_update call is checked against it from then on.
Questions about post_project_update
Append a dated narrative status update (Linear-style) to the project. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for post_project_update: 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 FeatureBoard. Nothing to install.
post_project_update 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 post_project_update 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 post_project_update. 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.
post_project_update is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue