enable_telemetry

Create a LOCAL-scoped telemetry profile (streaming/export destinations)

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

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/secure-ssid-centralmcp/enable-telemetry.md

WHAT IT DOES

What enable_telemetry does on API-Central

AI agents use enable_telemetry to create or update resources in API-Central, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.

RISK

Why enable_telemetry is rated Medium

This tool modifies network configuration by creating a new telemetry profile, which is a reversible write operation. It establishes streaming and export destinations for telemetry data collection. While it affects network monitoring infrastructure, the action is not destructive (it can be removed or modified), not financial, and not a direct code/command execution.

From the tool's definition The tool creates a telemetry profile with streaming and export destinations. The verb 'create' and the action of establishing new telemetry profiles indicates data modification rather than retrieval.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs enable_telemetry safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For enable_telemetry, this is the rule to start with:

enable_telemetry Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "enable_telemetry": {
      "limits": [
        {
          "counter": "enable_telemetry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every enable_telemetry call is checked against it from then on.

FAQ

Questions about enable_telemetry

What does the enable_telemetry tool do? +

Create a LOCAL-scoped telemetry profile (streaming/export destinations). It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on enable_telemetry? +

Register the API-Central MCP server in PolicyLayer and add a rule for enable_telemetry: 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 API-Central. Nothing to install.

What risk level is enable_telemetry? +

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

Can I rate-limit enable_telemetry? +

Yes. Add a rate_limit block to the enable_telemetry 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 enable_telemetry completely? +

Set action: deny in the PolicyLayer policy for enable_telemetry. 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 enable_telemetry? +

enable_telemetry is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →