Get highlighted tweets from a user's profile.
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.
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:
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:
{
"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.
Free to start. No card required.
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.
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.
get_user_highlights is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
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.