Low Risk

gong_list_users

List all users in your workspace. Returns user names, IDs, email addresses, roles, and activity status.

Risk signalsBulk/mass operation — affects multiple targets

Part of the Gong server.

gong_list_users is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE GONG →

Free to start. No card required.

AI agents call gong_list_users to retrieve information from Gong without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though gong_list_users only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gong_list_users": {}
  }
}

See the full Gong policy for all 25 tools.

Get this rule live on your own Gong server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GONG →

View all 25 tools →

These attack patterns abuse exactly the kind of access gong_list_users gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so gong_list_users only ever does what you allow.

SECURE GONG →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the gong_list_users tool do? +

List all users in your workspace. Returns user names, IDs, email addresses, roles, and activity status.. It is categorised as a Read tool in the Gong MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gong_list_users? +

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

What risk level is gong_list_users? +

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

Can I rate-limit gong_list_users? +

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

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

gong_list_users is provided by the Gong MCP server (https://gateway.pipeworx.io/gong/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gong tool call.

Deterministic rules across all 25 Gong tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.