AI agents call get_profile to retrieve information from Twitter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user profile data (a query operation) with no capability to modify, delete, or execute external actions. It is a straightforward read operation on publicly available Twitter user information. The severity is low because profile data is typically public and cannot cause significant harm if accessed by an AI agent.
From the tool's definition Tool name 'get_profile' and description 'Get a Twitter user' indicate retrieval of public user profile information without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_profile gives an agent:
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_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_profile": {}
}
}get_profile 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 a Twitter user. It is categorised as a Read tool in the Twitter MCP Server, which means it retrieves data without modifying state.
Register the Twitter MCP server in PolicyLayer and add a rule for get_profile: 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.
get_profile 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_profile 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_profile. 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_profile 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.
Start from Twitter, 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.
13 Twitter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.