set_standard
Set — and LOCK — how much rigor a project
This record as markdown: /tools/ai-featureboard-featureboard/set-standard.md
What set_standard does on FeatureBoard
AI agents use set_standard 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_standard is rated Medium
This tool creates or modifies project configuration (standards/rigor levels) in a reversible manner. While it includes a locking mechanism, the primary action is setting/updating a project parameter rather than executing external operations or irreversibly destroying data. It affects how the project board operates but remains within Write category.
From the tool's definition Tool name "set_standard" and description "Set — and LOCK — how much rigor a project" indicates modification of project configuration settings. The term "LOCK" suggests making a change that becomes fixed/enforced.
Attacks that exploit this kind of access
The rule that runs set_standard 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_standard, this is the rule to start with:
set_standard 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_standard call is checked against it from then on.
Questions about set_standard
Set — and LOCK — how much rigor a project. 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_standard: 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_standard 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_standard 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_standard. 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_standard 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