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

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.

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

Questions about edit_site_section

What does the edit_site_section tool do? +

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.

How do I enforce a policy on edit_site_section? +

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.

What risk level is edit_site_section? +

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

Can I rate-limit edit_site_section? +

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.

How do I block edit_site_section completely? +

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.

What MCP server provides edit_site_section? +

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.

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