Get time-bucketed post counts for all posts (full archive - requires Academic Research or Enterprise access)
AI agents call getPostCountsAll to retrieve information from X Com MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves post count statistics across time periods from the full X.com archive. It performs a read-only operation with no side effects, no data modification, and no irreversible actions. While it requires elevated access (Academic Research or Enterprise), it simply returns analytical/statistical data about posts.
From the tool's definition Tool name and description: 'Get time-bucketed post counts for all posts' — retrieves aggregated historical data with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access getPostCountsAll gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and X Com MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getPostCountsAll:
{
"version": "1",
"default": "deny",
"tools": {
"getPostCountsAll": {}
}
}getPostCountsAll 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 time-bucketed post counts for all posts (full archive - requires Academic Research or Enterprise access). It is categorised as a Read tool in the X Com MCP Server MCP Server, which means it retrieves data without modifying state.
Register the X Com MCP Server MCP server in PolicyLayer and add a rule for getPostCountsAll: 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 X Com MCP Server. Nothing to install.
getPostCountsAll 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 getPostCountsAll 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 getPostCountsAll. 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.
getPostCountsAll is provided by the X Com MCP Server MCP server (tiovikram/x.com-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from X Com MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 X Com MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.