get_source_channels_distribution

Get distribution of ticket source channels

Server Respona Dashboard MCP Server raihan0824/mcp-respona-dashboard
Category Read
Risk class Low
Parameters 00 required

What get_source_channels_distribution does on Respona Dashboard MCP Server

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

Why get_source_channels_distribution needs a policy

This tool retrieves and queries dashboard analytics data (distribution statistics) with no side effects. It follows the Read category pattern of other sibling tools (get_dashboard_analytics, get_status_distribution, get_priority_distribution) that fetch and present existing data. The blast radius of misuse is minimal—an agent could only access metadata about ticket source channels.

From the tool's definition Tool name 'get_source_channels_distribution' and description 'Get distribution of ticket source channels' indicate a query operation that retrieves aggregated data about ticket sources without modifying, deleting, or executing external operations.

Questions about get_source_channels_distribution

What does the get_source_channels_distribution tool do? +

Get distribution of ticket source channels. It is categorised as a Read tool in the Respona Dashboard MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_source_channels_distribution? +

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

What risk level is get_source_channels_distribution? +

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

Can I rate-limit get_source_channels_distribution? +

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

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

get_source_channels_distribution is provided by the Respona Dashboard MCP Server MCP server (raihan0824/mcp-respona-dashboard). 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.