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

set_branding

Set the project

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-branding.md

What set_branding does on FeatureBoard

AI agents use set_branding 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_branding is rated Medium

This tool creates or modifies project branding configuration, which is reversible and does not delete data or execute arbitrary code. It falls clearly into the Write category (create/update operations). Severity is medium because misconfigured branding could affect team productivity and project presentation, but the impact is limited to aesthetic/organizational scope without financial or destructive consequences.

From the tool's definition Tool name 'set_branding' and description 'Set the project' indicate modification of project configuration/branding settings. The verb 'set' confirms a write operation that modifies data state.

Questions about set_branding

What does the set_branding tool do? +

Set the 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.

How do I enforce a policy on set_branding? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for set_branding: 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_branding? +

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

Can I rate-limit set_branding? +

Yes. Add a rate_limit block to the set_branding 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_branding completely? +

Set action: deny in the PolicyLayer policy for set_branding. 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_branding? +

set_branding 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.