Low Risk

twitter_scrape_profile

Use this when you need to look up a Twitter/X user profile by username or URL. Returns structured profile data including bio, follower/following counts, tweet count, verification status, and recent activity. 1. username: the @handle 2. displayName: full name 3. bio: profile description text 4. fo...

Part of the Twitter Scraper API server.

twitter_scrape_profile 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 TWITTER SCRAPER API →

Free to start. No card required.

AI agents call twitter_scrape_profile to retrieve information from Twitter Scraper API 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 twitter_scrape_profile 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": {
    "twitter_scrape_profile": {}
  }
}

See the full Twitter Scraper API policy for all 3 tools.

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

ENFORCE ON MY TWITTER SCRAPER API →

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

SECURE TWITTER SCRAPER API →

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

What does the twitter_scrape_profile tool do? +

Use this when you need to look up a Twitter/X user profile by username or URL. Returns structured profile data including bio, follower/following counts, tweet count, verification status, and recent activity. 1. username: the @handle 2. displayName: full name 3. bio: profile description text 4. followers: follower count 5. following: following count 6. tweetCount: total tweets posted 7. verified: blue checkmark status 8. createdAt: account creation date 9. avatarUrl: profile picture URL 10. bannerUrl: header image URL 11. location: stated location 12. website: linked URL 13. pinnedTweet: text of pinned tweet if any Example output: { "username": "elonmusk", "displayName": "Elon Musk", "bio": "...", "followers": 195000000, "following": 850, "tweetCount": 45000, "verified": true, "createdAt": "2009-06-02" } Use this FOR social media due diligence, influencer research, competitor monitoring, or verifying the legitimacy of an account before trusting its content. Do NOT use for tweet search -- use twitter_search_tweets instead. Do NOT use for trust/security scoring -- use trust_score_evaluate instead. Do NOT use for email lookup from social -- use email_find_by_name instead.. It is categorised as a Read tool in the Twitter Scraper API MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on twitter_scrape_profile? +

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

What risk level is twitter_scrape_profile? +

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

Can I rate-limit twitter_scrape_profile? +

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

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

twitter_scrape_profile is provided by the Twitter Scraper API MCP server (https://twitter-scraper.api.klymax402.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Twitter Scraper API tool call.

Deterministic rules across all 3 Twitter Scraper API 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.