get_user_by_username

THE RISK

Low Risk

Why get_user_by_username needs a policy

This tool retrieves user profile information from Twitter/X via a username lookup. It performs a query operation that returns data without side effects—no data is created, modified, deleted, or financial transactions are initiated. The action is read-only, placing it in the Read category with low severity as it only exposes publicly available profile information.

From the tool's definition Tool name 'get_user_by_username' and description 'Get detailed user profile information by Twitter username' indicate data retrieval with no modification or execution capability.

Documented attack patterns abuse exactly the kind of access get_user_by_username gives an agent:

POLICY

How to control get_user_by_username

PolicyLayer is an MCP gateway — it sits between your AI agents and SocialData MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_by_username:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_user_by_username": {}
  }
}

get_user_by_username is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register SocialData MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SocialData MCP Server tools

Destructive delete_monitor Delete an active monitor. Write create_pump_fun_monitor Create a monitor for pump.fun coin mentions on Twitter. Write create_user_following_monitor Create a monitor for when a user follows someone new. Write create_user_profile_monitor Create a monitor for user profile changes. Write create_user_tweets_monitor Create a monitor for new tweets from a specific user. Write edit_monitor_webhook Edit or remove webhook URL for a specific monitor. Write set_global_webhook Set global webhook URL for all monitors. Read analyze_tweet_engagement Get comprehensive engagement data for a tweet including comments, retweets, and quotes.

All 41 SocialData MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_user_by_username

What does the get_user_by_username tool do? +

Get detailed user profile information by Twitter username. It is categorised as a Read tool in the SocialData MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user_by_username? +

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

What risk level is get_user_by_username? +

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

Can I rate-limit get_user_by_username? +

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

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

get_user_by_username is provided by the SocialData MCP Server MCP server (thesethrose/socialdata-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SocialData MCP Server tool call.

Start from SocialData MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →