set_page_seo
Set SEO for the home page (omit slug, or slug=
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.
Attacks that exploit this kind of access
The rule that runs set_page_seo 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 set_page_seo, this is the rule to start with:
set_page_seo 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 set_page_seo call is checked against it from then on.
Questions about set_page_seo
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.
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.
set_page_seo 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 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.
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.
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.
This server
Across the catalogue