feedback_stats

Get a quick summary of project feedback statistics - total count, resolved/unresolved breakdown, feedback by type, and recent activity

Server Feedbucket MCP Server swiftcomza/feedbucket-mcp
Category Read
Risk class Low
Parameters 00 required

What feedback_stats does on Feedbucket MCP Server

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

Why feedback_stats needs a policy

This tool retrieves aggregated feedback statistics and metrics without creating, modifying, deleting, or executing any operations. It is purely informational with no side effects, placing it in the Read category. Severity is low because misuse would only expose feedback metadata/summaries, not sensitive individual feedback content or enable destructive actions.

From the tool's definition Tool description indicates 'Get a quick summary' of feedback statistics including counts and breakdowns. No modification, deletion, or execution of external operations.

Questions about feedback_stats

What does the feedback_stats tool do? +

Get a quick summary of project feedback statistics - total count, resolved/unresolved breakdown, feedback by type, and recent activity. It is categorised as a Read tool in the Feedbucket MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on feedback_stats? +

Register the Feedbucket MCP Server MCP server in PolicyLayer and add a rule for feedback_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 Feedbucket MCP Server. Nothing to install.

What risk level is feedback_stats? +

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

Can I rate-limit feedback_stats? +

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

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

feedback_stats is provided by the Feedbucket MCP Server MCP server (swiftcomza/feedbucket-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.