log_work
Append a work event to the board
This record as markdown: /tools/ai-featureboard-featureboard/log-work.md
What log_work does on FeatureBoard
AI agents use log_work 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 log_work is rated Medium
Appending a work event is a Write operation: it creates new data (a log entry) on the project board without permanently destroying existing data or executing arbitrary code. The severity is low because logging work events typically has minimal blast radius—the data can be edited or deleted, and misuse would produce spurious log entries rather than financial loss or system compromise.
From the tool's definition Tool description states 'Append a work event to the board' — this is a create/add operation that records work activity. The name 'log_work' and verb 'append' indicate reversible modification of board state.
Attacks that exploit this kind of access
The rule that runs log_work 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 log_work, this is the rule to start with:
log_work 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 log_work call is checked against it from then on.
Questions about log_work
Append a work event to the board. 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 log_work: 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.
log_work 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 log_work 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 log_work. 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.
log_work 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