get_work_packet
Assemble a focused brief for one ticket before you work it: scope, linked-issue details, code location + custom project prompt, scratchpad mentions, the ticket
This record as markdown: /tools/ai-featureboard-featureboard/get-work-packet.md
What get_work_packet does on FeatureBoard
AI agents call get_work_packet 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_packet is rated Low
This tool queries and retrieves information from the project board to present context about a ticket. It performs no side effects—no creation, modification, deletion, or code execution. The purpose is to gather data to inform an AI agent's work, not to perform that work itself. This is a pure read operation with minimal blast radius if misused.
From the tool's definition Tool retrieves a 'focused brief' containing scope, linked-issue details, code location, and ticket information. The verb 'assemble' and 'get' indicate data retrieval only. No modification, deletion, or execution of external operations is described.
Attacks that exploit this kind of access
The rule that runs get_work_packet 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_packet, this is the rule to start with:
get_work_packet 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_packet call is checked against it from then on.
Questions about get_work_packet
Assemble a focused brief for one ticket before you work it: scope, linked-issue details, code location + custom project prompt, scratchpad mentions, the ticket. 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_packet: 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_packet 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_packet 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_packet. 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_packet 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