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

set_site_analytics

Add an analytics snippet to every page of the site

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

Questions about set_site_analytics

What does the set_site_analytics tool do? +

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.

How do I enforce a policy on set_site_analytics? +

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.

What risk level is set_site_analytics? +

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

Can I rate-limit set_site_analytics? +

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.

How do I block set_site_analytics completely? +

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.

What MCP server provides set_site_analytics? +

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.

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