x_post
Retrieve an X post. Returns a public X post by numeric post id, including author, text, visible metrics, and a quoted post preview when present.
This record as markdown: /tools/crawlora-mcp/x-post.md
What x_post does on Crawlora
AI agents call x_post to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | X post id |
username | string | — | Expected author username. When provided, mismatched authors return 404. |
Parameters from the server's own tool schema.
Why x_post is rated Low
The tool only retrieves and returns publicly available data from X (Twitter) by post ID. No writes, executions, or modifications are performed. Low severity as it only reads public information.
From the tool's definition Retrieve an X post. Returns a public X post by numeric post id, including author, text, visible metrics, and a quoted post preview when present.
Attacks that exploit this kind of access
The rule that runs x_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x_post, this is the rule to start with:
x_post 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 Crawlora, apply this rule, and every x_post call is checked against it from then on.
Questions about x_post
Retrieve an X post. Returns a public X post by numeric post id, including author, text, visible metrics, and a quoted post preview when present. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
x_post accepts 2 parameters: id, username. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for x_post: 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 Crawlora. Nothing to install.
x_post 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 x_post 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 x_post. 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.
x_post is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue