analytics

Bulk/mass operation — affects multiple targets

Part of the Pipepost MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents call analytics to retrieve information from Pipepost without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON ANALYTICS

Even though analytics only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-mendlem-pipepost.yaml

tools:
  analytics:
    rules:
      - action: allow

See the full Pipepost policy for all 29 tools.

// DETAILS

Tool Name analytics

Category Read

MCP Server Pipepost MCP Server

Risk Level Low

// MORE PIPEPOST TOOLS

Destructive delete_draft Write activate Write bluesky_post Write cross_publish Write generate_social_posts Write linkedin_post Write mastodon_post Write publish

View all 29 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like analytics have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the analytics tool do? +

Fetch post views, reactions, and comments from every configured CMS platform (devto, ghost, hashnode, wordpress) and aggregate the totals. FREE. Requires platform credentials. Medium and Substack are listed but their APIs do not expose post-level analytics. Returns: { platforms: [{ platform, posts: [{ title, url, views?, reactions?, comments?, published_at? }], note? }], summary: { total_posts, total_views, total_reactions } }. Common errors: no platforms configured (VALIDATION_ERROR), upstream auth failure surfaces per-platform in 'note'.. It is categorised as a Read tool in the Pipepost MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analytics? +

Add a rule in your Intercept YAML policy under the tools section for analytics. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pipepost MCP server.

What risk level is analytics? +

analytics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit analytics? +

Yes. Add a rate_limit block to the analytics rule in your Intercept 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.

How do I block analytics completely? +

Set action: deny in the Intercept policy for analytics. 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.

What MCP server provides analytics? +

analytics is provided by the Pipepost MCP server (pipepost-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

analytics

Enforce policies on Pipepost