user_id

Get Meta user ID or current user info

Part of the Meta Ads MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents call user_id to retrieve information from Meta Ads 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.

// WHY ENFORCE A POLICY ON USER_ID

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

// RECOMMENDED POLICY

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

co-pipeboard-meta-ads-mcp.yaml

tools:
  user_id:
    rules:
      - action: allow

See the full Meta Ads policy for all 47 tools.

// DETAILS

Tool Name user_id

Category Read

MCP Server Meta Ads MCP Server

Risk Level Low

// MORE META ADS TOOLS

Write bid_amount Write bid_constraints Write bid_strategy Write budget_value Write budget_value_type Write call_to_action_type Write daily_budget Write description

View all 47 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like user_id have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the user_id tool do? +

Get Meta user ID or current user info. It is categorised as a Read tool in the Meta Ads MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on user_id? +

Add a rule in your Intercept YAML policy under the tools section for user_id. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Meta Ads MCP server.

What risk level is user_id? +

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

Can I rate-limit user_id? +

Yes. Add a rate_limit block to the user_id rule in your Intercept 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 user_id completely? +

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

user_id is provided by the Meta Ads MCP server (meta-ads-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

user_id

Enforce policies on Meta Ads