edit_site_section
Live editor: patch one website section by index (heading and/or body), or append a new section when index is omitted. Re-renders the page.
This record as markdown: /tools/ai-featureboard-featureboard/edit-site-section.md
What edit_site_section does on FeatureBoard
AI agents use edit_site_section 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 edit_site_section is rated Medium
This tool modifies website content through patching existing sections or appending new ones, then re-renders the page. These are reversible Write operations (not Destructive since patches can be undone/reverted). The high severity reflects that an AI agent with this capability could modify live website content, affecting all users viewing that site.
From the tool's definition Tool performs 'patch' and 'append' operations on website sections; explicitly stated 're-renders the page' indicating persistent state changes.
Attacks that exploit this kind of access
The rule that runs edit_site_section 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 edit_site_section, this is the rule to start with:
edit_site_section 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 edit_site_section call is checked against it from then on.
Questions about edit_site_section
Live editor: patch one website section by index (heading and/or body), or append a new section when index is omitted. Re-renders the page. 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 edit_site_section: 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.
edit_site_section 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 edit_site_section 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 edit_site_section. 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.
edit_site_section 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