save_test_page
Create/overwrite a standalone HTML test/QA page under the project
This record as markdown: /tools/ai-featureboard-featureboard/save-test-page.md
What save_test_page does on FeatureBoard
AI agents use save_test_page 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 save_test_page is rated Medium
This tool creates or overwrites HTML files in the project, making it a Write operation (reversible modification of data/files). It is not Destructive because the operation can be undone by creating a new version or deleting the file.
From the tool's definition Tool description states 'Create/overwrite a standalone HTML test/QA page under the project' — explicitly creates or overwrites files, which is a write operation that modifies project state.
Attacks that exploit this kind of access
The rule that runs save_test_page 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 save_test_page, this is the rule to start with:
save_test_page 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 save_test_page call is checked against it from then on.
Questions about save_test_page
Create/overwrite a standalone HTML test/QA page under 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.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for save_test_page: 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.
save_test_page 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 save_test_page 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 save_test_page. 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.
save_test_page 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