posts_x
Fetch recent tweets from an X/Twitter user (up to 30 tweets with text, engagement, timestamps). Use for sentiment monitoring, content scraping, or thread analysis. Example call: {"username": "paulg"} Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/io-github-colinhughes2121-gocreative-agent-api/posts-x.md
What posts_x does on GoCreative Agent API
AI agents call posts_x to retrieve information from GoCreative Agent API 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 |
|---|---|---|---|
username | string | Yes |
Parameters from the server's own tool schema.
Why posts_x is rated Low
This tool retrieves publicly available data from X/Twitter (up to 30 tweets with metadata). No data is created, modified, deleted, or overwritten. The operation is non-destructive and produces no side effects beyond network retrieval. While it enables content scraping and surveillance, these are read operations. Severity is low because misuse retrieves only public data already accessible to any X user.
From the tool's definition Tool description states 'Fetch recent tweets' and lists use cases as 'sentiment monitoring, content scraping, or thread analysis' — all read-only operations. The example call retrieves public tweets without modification.
Attacks that exploit this kind of access
The rule that runs posts_x safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoCreative Agent API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For posts_x, this is the rule to start with:
posts_x 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 GoCreative Agent API, apply this rule, and every posts_x call is checked against it from then on.
Questions about posts_x
Fetch recent tweets from an X/Twitter user (up to 30 tweets with text, engagement, timestamps). Use for sentiment monitoring, content scraping, or thread analysis. Example call: {"username": "paulg"} Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the GoCreative Agent API MCP Server, which means it retrieves data without modifying state.
posts_x accepts 1 parameter: username. Required: username. The full parameter table on this page comes from the server's own tool schema.
Register the GoCreative Agent API MCP server in PolicyLayer and add a rule for posts_x: 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 GoCreative Agent API. Nothing to install.
posts_x 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 posts_x 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 posts_x. 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.
posts_x is provided by the GoCreative Agent API MCP server (https://api.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoCreative Agent API, and thousands of servers like it.
This server
Across the catalogue