adaptercloud_tags_analytics
Time-bucketed analytics for a tag: assignmentCount, uniqueUsers, uniqueEntities, and entityType breakdown over the [from, to] window.
This record as markdown: /tools/burdenoff-adaptercloud-mcp/adaptercloud-tags-analytics.md
What adaptercloud_tags_analytics does on Adaptercloud
AI agents call adaptercloud_tags_analytics to retrieve information from Adaptercloud without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | End of the window in ISO-8601 (DateTime) |
from | string | Yes | Start of the window in ISO-8601 (DateTime) |
tagId | string | Yes | Tag ID to analyse |
Parameters from the server's own tool schema.
Why adaptercloud_tags_analytics is rated Low
Even though adaptercloud_tags_analytics only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs adaptercloud_tags_analytics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adaptercloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adaptercloud_tags_analytics, this is the rule to start with:
adaptercloud_tags_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Adaptercloud, apply this rule, and every adaptercloud_tags_analytics call is checked against it from then on.
Questions about adaptercloud_tags_analytics
Time-bucketed analytics for a tag: assignmentCount, uniqueUsers, uniqueEntities, and entityType breakdown over the [from, to] window. It is categorised as a Read tool in the Adaptercloud MCP Server, which means it retrieves data without modifying state.
adaptercloud_tags_analytics accepts 3 parameters: to, from, tagId. Required: to, from, tagId. The full parameter table on this page comes from the server's own tool schema.
Register the Adaptercloud MCP server in PolicyLayer and add a rule for adaptercloud_tags_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 Adaptercloud. Nothing to install.
adaptercloud_tags_analytics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the adaptercloud_tags_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 adaptercloud_tags_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.
adaptercloud_tags_analytics is provided by the Adaptercloud MCP server (@burdenoff/adaptercloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adaptercloud, and thousands of servers like it.
This server
Across the catalogue