get_feed_statistics

Get comprehensive feed statistics and analysis

SERVERContextForge MCP Gateway SOURCEjrmatherly/mcp-context-forge

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jrmatherly-mcp-context-forge/get-feed-statistics.md

WHAT IT DOES

What get_feed_statistics does on ContextForge MCP Gateway

AI agents call get_feed_statistics to retrieve information from ContextForge MCP Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_feed_statistics is rated Low

This tool performs a read-only query to fetch statistics and analytical data. There are no indications of side effects, modifications, deletions, code execution, or financial operations. The verb 'Get' and the passive analytical purpose place it squarely in the Read category.

From the tool's definition The tool name 'get_feed_statistics' and description 'Get comprehensive feed statistics and analysis' indicates a retrieval operation that returns data without modifying, deleting, or executing external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_feed_statistics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_feed_statistics, this is the rule to start with:

get_feed_statistics Allowed

get_feed_statistics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_feed_statistics": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every get_feed_statistics call is checked against it from then on.

FAQ

Questions about get_feed_statistics

What does the get_feed_statistics tool do? +

Get comprehensive feed statistics and analysis. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_feed_statistics? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for get_feed_statistics: 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 ContextForge MCP Gateway. Nothing to install.

What risk level is get_feed_statistics? +

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

Can I rate-limit get_feed_statistics? +

Yes. Add a rate_limit block to the get_feed_statistics 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.

How do I block get_feed_statistics completely? +

Set action: deny in the PolicyLayer policy for get_feed_statistics. 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 get_feed_statistics? +

get_feed_statistics is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ContextForge MCP Gateway, and thousands of servers like it.

This server

All 221 ContextForge MCP Gateway tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →