get_user_relationships

THE RISK

Low Risk

Why get_user_relationships needs a policy

This tool retrieves user relationship data without side effects. It queries existing information about a user but does not create, modify, delete, or execute any actions. The minimal blast radius from misuse (retrieving user information) and read-only nature place it in the Read category with low severity.

From the tool's definition Tool name 'get_user_relationships' and description 'Get a user' indicate a retrieval operation that fetches user information without modification.

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

POLICY

How to control get_user_relationships

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

policy.json

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

get_user_relationships 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 Twitter — 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 Twitter tools

Write follow_user Follow or unfollow a Twitter user Write like_tweet Like or unlike a tweet Write retweet Retweet or undo retweet of a tweet Write create_note Create a new note Write create_thread Create a Twitter thread (a series of connected tweets) Write post_tweet Post a new tweet, optionally with media or as a quote tweet Read get_list_tweets Get tweets from a Twitter list Read get_profile Get a Twitter user

All 13 Twitter 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_relationships

What does the get_user_relationships tool do? +

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

How do I enforce a policy on get_user_relationships? +

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

What risk level is get_user_relationships? +

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

Can I rate-limit get_user_relationships? +

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

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

get_user_relationships is provided by the Twitter MCP server (twitter-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 Twitter tool call.

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

CHECK YOUR STACK →