set_project_config
Update a board
This record as markdown: /tools/ai-featureboard-featureboard/set-project-config.md
What set_project_config does on FeatureBoard
AI agents use set_project_config 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_project_config is rated Medium
This tool creates or modifies data reversibly by updating board/project configuration. It is not destructive (data can be reverted), not financial, and not execute (no code/command execution). The 'medium' severity reflects that misconfiguration could disrupt workflow or expose sensitive settings, but the scope is limited to project metadata rather than mass data deletion or code execution.
From the tool's definition Tool name 'set_project_config' and description 'Update a board' indicate modification of project configuration data.
Attacks that exploit this kind of access
The rule that runs set_project_config 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_project_config, this is the rule to start with:
set_project_config 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_project_config call is checked against it from then on.
Questions about set_project_config
Update 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_project_config: 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_project_config 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_project_config 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_project_config. 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_project_config 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