New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

set_project_config

Update a board

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about set_project_config

What does the set_project_config tool do? +

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.

How do I enforce a policy on set_project_config? +

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.

What risk level is set_project_config? +

set_project_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_project_config? +

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.

How do I block set_project_config completely? +

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.

What MCP server provides set_project_config? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FeatureBoard's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.