Retrieve detailed analytics and metrics for posts.
AI agents call getPostsAnalytics to retrieve information from Xdevplatform/xmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns analytics data about posts, which is a read-only operation with no side effects. Analytics retrieval does not create, modify, delete, or execute operations. The low severity reflects that even if exposed to an AI agent, retrieving analytics poses minimal risk.
From the tool's definition Tool name and description indicate retrieval: 'Retrieve detailed analytics and metrics for posts'. No modification, deletion, or execution of external operations implied.
Attacks that exploit this kind of access
Retrieve detailed analytics and metrics for posts. It is categorised as a Read tool in the Xdevplatform/xmcp MCP Server, which means it retrieves data without modifying state.
Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for getPostsAnalytics: 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 Xdevplatform/xmcp. Nothing to install.
getPostsAnalytics 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 getPostsAnalytics 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 getPostsAnalytics. 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.
getPostsAnalytics is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
getPostsAnalytics is one line of Xdevplatform/x's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →