Get user information for up to 100 Twitter users by their IDs.
AI agents call get_multiple_users_by_ids 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 authorized user information from Twitter/X without modifying, deleting, or executing any operations. It is a straightforward data query operation that poses minimal risk when called by an AI agent, as it only accesses existing user data without any destructive, financial, or executable implications.
From the tool's definition Tool name is 'get_multiple_users_by_ids' and description states 'Get user information for up to 100 Twitter users by their IDs.' The verb 'Get' and the informational nature of retrieving user profiles indicate a read-only operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_multiple_users_by_ids 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_multiple_users_by_ids:
{
"version": "1",
"default": "deny",
"tools": {
"get_multiple_users_by_ids": {}
}
} get_multiple_users_by_ids 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 user information for up to 100 Twitter users by their IDs. 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_multiple_users_by_ids: 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_multiple_users_by_ids 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_multiple_users_by_ids 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_multiple_users_by_ids. 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_multiple_users_by_ids 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.