twitter.users.profile

Get a Twitter/X user profile by username. Returns display name, bio, follower/following count, tweet count, verified status, profile image, location, and account creation date.

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/twitter.users.profile.md

WHAT IT DOES

What twitter.users.profile does on Apibase

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

Parameter	Type	Required	Description
`user_id`	string	—	Twitter/X numeric user ID as alternative to username
`username`	string	—	Twitter/X username without @ (e.g. "elonmusk", "OpenAI")

Parameters from the server's own tool schema.

RISK

Why twitter.users.profile is rated Low

Retrieves publicly available user profile metadata with no side effects or data modification capability.

From the tool's definition Get a Twitter/X user profile by username. Returns display name, bio, follower/following count, tweet count

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs twitter.users.profile safely

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

twitter.users.profile Allowed

twitter.users.profile 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": {
    "twitter.users.profile": {}
  }
}

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

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

FAQ

Questions about twitter.users.profile

What does the twitter.users.profile tool do? +

Get a Twitter/X user profile by username. Returns display name, bio, follower/following count, tweet count, verified status, profile image, location, and account creation date. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does twitter.users.profile accept? +

twitter.users.profile accepts 2 parameters: user_id, username. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on twitter.users.profile? +

Register the Apibase MCP server in PolicyLayer and add a rule for twitter.users.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 Apibase. Nothing to install.

What risk level is twitter.users.profile? +

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

Can I rate-limit twitter.users.profile? +

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

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

twitter.users.profile is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

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