get_work_log
Read work-log entries, most-recent first. Optionally filter to one ticket. Returns entries plus a velocity rollup.
This record as markdown: /tools/ai-featureboard-featureboard/get-work-log.md
What get_work_log does on FeatureBoard
AI agents call get_work_log to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_work_log is rated Low
This tool retrieves and queries historical work log data without side effects. The description explicitly uses 'Read' as the primary action, returning entries and velocity metrics. There is no indication of modification, execution, or destructive capability. The only capability is data retrieval, making this a straightforward Read category tool with low severity risk.
From the tool's definition Tool name 'get_work_log' and description states 'Read work-log entries' with optional filtering and returns data. No mutation, creation, deletion, or execution semantics are present.
Attacks that exploit this kind of access
The rule that runs get_work_log 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 get_work_log, this is the rule to start with:
get_work_log 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 FeatureBoard, apply this rule, and every get_work_log call is checked against it from then on.
Questions about get_work_log
Read work-log entries, most-recent first. Optionally filter to one ticket. Returns entries plus a velocity rollup. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for get_work_log: 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.
get_work_log 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 get_work_log 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 get_work_log. 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.
get_work_log 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