x_profile_posts
List public X profile posts. Returns posts present in the first public profile page payload for an X username. The endpoint does not paginate replies, media-only tabs, or search results.
This record as markdown: /tools/crawlora-mcp/x-profile-posts.md
What x_profile_posts does on Crawlora
AI agents call x_profile_posts 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 |
|---|---|---|---|
limit | integer | — | Maximum posts returned from the first page payload. Defaults to 20 and must be 1-50. |
username | string | Yes | X username |
Parameters from the server's own tool schema.
Why x_profile_posts is rated Low
This tool retrieves and queries publicly available posts from X (Twitter) profiles. It has no side effects, does not modify data, execute code, delete content, or involve financial transactions. The read-only nature and public data access pattern clearly place it in the Read category with low severity, as misuse would only involve accessing information already public.
From the tool's definition Tool description states 'List public X profile posts' and 'Returns posts present in the first public profile page payload for an X username' — pure retrieval of publicly available data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs x_profile_posts 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_profile_posts, this is the rule to start with:
x_profile_posts 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_profile_posts call is checked against it from then on.
Questions about x_profile_posts
List public X profile posts. Returns posts present in the first public profile page payload for an X username. The endpoint does not paginate replies, media-only tabs, or search results. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
x_profile_posts accepts 2 parameters: limit, username. Required: username. 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_profile_posts: 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_profile_posts 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_profile_posts 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_profile_posts. 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_profile_posts 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