set_site_analytics
Add an analytics snippet to every page of the site
This record as markdown: /tools/ai-featureboard-featureboard/set-site-analytics.md
What set_site_analytics does on FeatureBoard
AI agents use set_site_analytics 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_site_analytics is rated Medium
This tool creates or modifies site configuration reversibly by adding analytics code. It does not delete data (not Destructive), does not move money (not Financial), and does not execute arbitrary code on demand (not Execute—it performs a specific, predefined modification). The Write category applies because it persistently changes site state.
From the tool's definition "Add an analytics snippet to every page of the site" - modifies site configuration by injecting tracking code into pages
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs set_site_analytics 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_site_analytics, this is the rule to start with:
set_site_analytics 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_site_analytics call is checked against it from then on.
Questions about set_site_analytics
Add an analytics snippet to every page of the site. 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_site_analytics: 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_site_analytics 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_site_analytics 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_site_analytics. 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_site_analytics 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