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

set_page_seo

Set SEO for the home page (omit slug, or slug=

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-page-seo.md

What set_page_seo does on FeatureBoard

AI agents use set_page_seo 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_page_seo is rated Medium

This tool modifies page metadata (SEO attributes like title, description, keywords) which is reversible data alteration. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), does not involve financial transactions (not Financial), and is not a simple read operation (not Read).

From the tool's definition Tool name 'set_page_seo' and description 'Set SEO for the home page' indicate creation or modification of metadata. The verb 'set' combined with 'SEO' (search engine optimization metadata) suggests updating page properties.

Questions about set_page_seo

What does the set_page_seo tool do? +

Set SEO for the home page (omit slug, or slug=. 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_page_seo? +

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

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

Can I rate-limit set_page_seo? +

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

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

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