get_live_count

A read tool on the Elevenlabs MCP server.

SERVERElevenlabs SOURCE@aiwerk/mcp-server-elevenlabs

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/get-live-count.md

WHAT IT DOES

What get_live_count does on Elevenlabs

AI agents call get_live_count to retrieve information from Elevenlabs 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
`agent_id`	string \| null	—	The id of an agent to restrict the analytics to.
`agent_ids`	object	—	Restrict analytics to the union of the given agents. Takes precedence over `agent_id` when both are supplied.

Parameters from the server's own tool schema.

RISK

Why get_live_count is rated Low

Even though get_live_count 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

RECOMMENDED RULE

The rule that runs get_live_count safely

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

get_live_count Allowed

get_live_count is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_live_count": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_live_count

What does the get_live_count tool do? +

get_live_count is a read tool on the Elevenlabs MCP server. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.

What parameters does get_live_count accept? +

get_live_count accepts 2 parameters: agent_id, agent_ids. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_live_count? +

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

What risk level is get_live_count? +

get_live_count is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_live_count? +

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

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

get_live_count is provided by the Elevenlabs MCP server (@aiwerk/mcp-server-elevenlabs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Elevenlabs, and thousands of servers like it.

This server

All 390 Elevenlabs tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →