Low Risk

get_user_highlights

Get highlighted tweets from a user's profile.

How to control get_user_highlights ↓

What get_user_highlights does on SocialData MCP Server

AI agents call get_user_highlights to retrieve information from SocialData MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_user_highlights needs a policy

This tool retrieves publicly available or user-accessible highlighted tweet data from a profile. It performs a query operation (get) that returns information without creating, modifying, deleting, or executing any actions. The operation is read-only and poses minimal risk even if misused by an AI agent, as it only exposes data that is already publicly visible on the user's profile.

From the tool's definition Tool name 'get_user_highlights' and description 'Get highlighted tweets from a user's profile' indicate data retrieval with no modification or side effects.

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

How to control get_user_highlights

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_highlights:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_user_highlights": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_user_highlights

What does the get_user_highlights tool do? +

Get highlighted tweets from a user's profile. 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_highlights? +

Register the SocialData MCP Server MCP server in PolicyLayer and add a rule for get_user_highlights: 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_highlights? +

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

Can I rate-limit get_user_highlights? +

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

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

get_user_highlights 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.

Free to start. No card required.

41 SocialData MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.