list_x_ads_accounts

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/hermoso/list-x-ads-accounts.md

WHAT IT DOES

What list_x_ads_accounts does on Hermoso

AI agents call list_x_ads_accounts to retrieve information from Hermoso without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_x_ads_accounts is rated Low

Even though list_x_ads_accounts 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.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_x_ads_accounts safely

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

list_x_ads_accounts Allowed

list_x_ads_accounts 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": {
    "list_x_ads_accounts": {}
  }
}

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

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

FAQ

Questions about list_x_ads_accounts

What does the list_x_ads_accounts tool do? +

List the X (Twitter) ad accounts this profile can act on, with the PERMISSION LEVEL held on each so you can tell an admin grant from a read-only one before attempting a write. X grants API access PER AD ACCOUNT, not per app: the customer adds Hermoso’s X user to their ad account at business.x.com -> Account access, and it appears here. Read-only, free. It is categorised as a Read tool in the Hermoso MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_x_ads_accounts? +

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

What risk level is list_x_ads_accounts? +

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

Can I rate-limit list_x_ads_accounts? +

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

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

list_x_ads_accounts is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hermoso, and thousands of servers like it.

This server

All 896 Hermoso tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

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