Get recent tweets from a specific user. Args: user_id: Twitter user ID (get from twitter_get_user). max_results: Number of tweets (5-100, default 10).
AI agents call twitter_get_user_tweets to retrieve information from autoMate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation with no side effects. It queries publicly or user-accessible tweet data without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an AI agent would only retrieve tweets that the authenticated user already has permission to access.
From the tool's definition The tool retrieves recent tweets from a specific user via 'Get recent tweets' with read-only parameters (user_id, max_results). No modification, deletion, or execution capabilities are present.
Documented attack patterns abuse exactly the kind of access twitter_get_user_tweets gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for twitter_get_user_tweets:
{
"version": "1",
"default": "deny",
"tools": {
"twitter_get_user_tweets": {}
}
} twitter_get_user_tweets 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 recent tweets from a specific user. Args: user_id: Twitter user ID (get from twitter_get_user). max_results: Number of tweets (5-100, default 10). It is categorised as a Read tool in the autoMate MCP Server, which means it retrieves data without modifying state.
Register the autoMate MCP server in PolicyLayer and add a rule for twitter_get_user_tweets: 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 autoMate. Nothing to install.
twitter_get_user_tweets 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 twitter_get_user_tweets 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 twitter_get_user_tweets. 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.
twitter_get_user_tweets is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.