New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_channel_activity_trend

Channel activity trend. Per-channel daily message count sparkline and active member count over the lookback window.

SERVERTodo for AI MCP Server SOURCEtodo-for-ai/todo-for-ai-mcp
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/todo-for-ai-todo-for-ai-mcp/get-channel-activity-trend.md

What get_channel_activity_trend does on Todo for AI MCP Server

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

Why get_channel_activity_trend is rated Low

Even though get_channel_activity_trend only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about get_channel_activity_trend

What does the get_channel_activity_trend tool do? +

Channel activity trend. Per-channel daily message count sparkline and active member count over the lookback window. It is categorised as a Read tool in the Todo for AI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_channel_activity_trend? +

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

What risk level is get_channel_activity_trend? +

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

Can I rate-limit get_channel_activity_trend? +

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

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

get_channel_activity_trend is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Todo for AI MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Todo for AI MCP Server's. Pull the full record:

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.