get_feed_stats

Get platform-wide aggregate statistics for the PEPTOMA research feed. Returns total analyses, average bioactivity and confidence scores, total annotations, total votes, recent activity count (last 24h), and a breakdown of submissions by disease target.

Server Peptoma peptoma/mcp
Category Read
Risk class Low
Parameters 00 required

What get_feed_stats does on Peptoma

AI agents call get_feed_stats to retrieve information from Peptoma without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_feed_stats needs a policy

This tool retrieves and queries platform-wide summary data without modifying, deleting, executing code, or triggering external operations. It has no side effects and poses minimal risk—the returned statistics are already public aggregate information from the research platform. A misused AI agent cannot cause harm by calling this tool.

From the tool's definition Tool description explicitly states it 'Returns' aggregate statistics (total analyses, average scores, annotations, votes, activity counts, and breakdowns). Uses read-only verbs: 'Get platform-wide aggregate statistics'.

Questions about get_feed_stats

What does the get_feed_stats tool do? +

Get platform-wide aggregate statistics for the PEPTOMA research feed. Returns total analyses, average bioactivity and confidence scores, total annotations, total votes, recent activity count (last 24h), and a breakdown of submissions by disease target. It is categorised as a Read tool in the Peptoma MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_feed_stats? +

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

What risk level is get_feed_stats? +

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

Can I rate-limit get_feed_stats? +

Yes. Add a rate_limit block to the get_feed_stats 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_stats completely? +

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

get_feed_stats is provided by the Peptoma MCP server (peptoma/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.