Low Risk

getTwitterUser

Get Twitter user profile by ID or username. Use identifierType="id" for numeric user ID, identifierType="username" for username. For username: Use ONLY when you have the precise username (e.g., "elonmusk"). For person names or fuzzy search, use searchTwitterUsers instead. Optional fields paramete...

Part of the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) server.

getTwitterUser 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 SOCIAL MEDIA SEARCH API — TWITTER, INSTAGRAM, REDDIT, TIKTOK (XPOZ) →

Free to start. No card required.

AI agents call getTwitterUser to retrieve information from Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) 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 getTwitterUser 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": {
    "getTwitterUser": {}
  }
}

See the full Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) policy for all 48 tools.

Get this rule live on your own Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SOCIAL MEDIA SEARCH API — TWITTER, INSTAGRAM, REDDIT, TIKTOK (XPOZ) →

View all 48 tools →

These attack patterns abuse exactly the kind of access getTwitterUser 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 getTwitterUser only ever does what you allow.

SECURE SOCIAL MEDIA SEARCH API — TWITTER, INSTAGRAM, REDDIT, TIKTOK (XPOZ) →

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

What does the getTwitterUser tool do? +

Get Twitter user profile by ID or username. Use identifierType="id" for numeric user ID, identifierType="username" for username. For username: Use ONLY when you have the precise username (e.g., "elonmusk"). For person names or fuzzy search, use searchTwitterUsers instead. Optional fields parameter for performance (default: ["id", "username", "name"]). Available fields: id, profileImageUrl, profileBannerUrl, profileInterstitialType, status, username, verifiedType, name, description, location, protected, verified, followersCount, followingCount, tweetCount, listedCount, likesCount, mediaCount, pinnedTweetId, source, nLang, nLangsFiltered, label, labelType, isVerified, modifiedAt, createdAt, verifiedSinceDatetime, accountBasedIn, locationAccurate, usernameChanges, lastUsernameChangeDatetime. NOTE: Use "tweetCount" not "statusesCount". Returns: single user profile with id, username, name, bio, followers_count, following_count, tweet_count, created_at, authenticity_score, inauthentic_type. This is a safe, read-only tool for analyzing searchable information.. It is categorised as a Read tool in the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTwitterUser? +

Register the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server in PolicyLayer and add a rule for getTwitterUser: 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 Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ). Nothing to install.

What risk level is getTwitterUser? +

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

Can I rate-limit getTwitterUser? +

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

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

getTwitterUser is provided by the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server (https://mcp.xpoz.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) tool call.

Deterministic rules across all 48 Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) 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.