getTweetById
Get a specific tweet by its ID from X/Twitter. Returns the full tweet with author info and engagement metrics.
This record as markdown: /tools/nanidao-agentek/gettweetbyid.md
What getTweetById does on Agentek Eth
AI agents call getTweetById to retrieve information from Agentek Eth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getTweetById is rated Low
This tool retrieves publicly available tweet data from X/Twitter. It performs a read-only query operation that does not modify data, execute code, delete content, or move funds. The blast radius of misuse is minimal—an agent could only retrieve tweets that are already public, with no capability to alter or delete them. This is a straightforward Read category tool.
From the tool's definition Tool description states 'Get a specific tweet by its ID from X/Twitter. Returns the full tweet with author info and engagement metrics.' The verbs 'Get' and 'Returns' indicate data retrieval with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs getTweetById safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentek Eth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getTweetById, this is the rule to start with:
getTweetById is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agentek Eth, apply this rule, and every getTweetById call is checked against it from then on.
Questions about getTweetById
Get a specific tweet by its ID from X/Twitter. Returns the full tweet with author info and engagement metrics. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for getTweetById: 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 Agentek Eth. Nothing to install.
getTweetById 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 getTweetById 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 getTweetById. 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.
getTweetById is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentek Eth, and thousands of servers like it.
This server
Across the catalogue