suggest_test_stub
Generate a boilerplate test file (path + node:test content) for a ticket, derived from its title/description and the board
This record as markdown: /tools/ai-featureboard-featureboard/suggest-test-stub.md
What suggest_test_stub does on FeatureBoard
AI agents call suggest_test_stub 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 suggest_test_stub is rated Low
The tool generates/suggests content (a test stub) based on ticket data. It appears to derive and return content rather than write it to disk or execute it. 'Generate' here is used in the sense of producing output for the user to review, not persisting it. Severity is low since it only reads ticket metadata and produces a text suggestion.
From the tool's definition Generate a boilerplate test file (path + node:test content) for a ticket, derived from its title/description and the board
Attacks that exploit this kind of access
The rule that runs suggest_test_stub 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 suggest_test_stub, this is the rule to start with:
suggest_test_stub 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 suggest_test_stub call is checked against it from then on.
Questions about suggest_test_stub
Generate a boilerplate test file (path + node:test content) for a ticket, derived from its title/description and the board. 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 suggest_test_stub: 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.
suggest_test_stub 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 suggest_test_stub 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 suggest_test_stub. 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.
suggest_test_stub 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