set_scratchpad
Overwrite a board
This record as markdown: /tools/ai-featureboard-featureboard/set-scratchpad.md
What set_scratchpad does on FeatureBoard
AI agents use set_scratchpad 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 set_scratchpad is rated Medium
The action is reversible (the previous board state could theoretically be recovered or re-set), making it Write rather than Destructive. However, overwriting a board is a significant mutation of project state that could lose unsaved work, warranting high severity. The blast radius is elevated because an AI agent could accidentally clear all tasks or planning data if misdirected or confused about intent.
From the tool's definition Tool description states 'Overwrite a board' — a modification that replaces existing content.
Attacks that exploit this kind of access
The rule that runs set_scratchpad 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 set_scratchpad, this is the rule to start with:
set_scratchpad 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 set_scratchpad call is checked against it from then on.
Questions about set_scratchpad
Overwrite a 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 set_scratchpad: 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.
set_scratchpad 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 set_scratchpad 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 set_scratchpad. 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.
set_scratchpad 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