get_channel_history

Get message history from a channel

SERVERNcp SOURCE@portel/ncp

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/io-github-portel-dev-ncp/get-channel-history.md

WHAT IT DOES

What get_channel_history does on Ncp

AI agents call get_channel_history to retrieve information from Ncp 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_channel_history is rated Low

This tool retrieves historical message data from a channel without creating, modifying, deleting, or executing any operations. The action is purely informational and read-only, making it a Read category risk with low severity since accessing message history has minimal blast radius compared to destructive or financial operations.

From the tool's definition Tool name 'get_channel_history' and description 'Get message history from a channel' both indicate a retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_channel_history safely

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

get_channel_history Allowed

get_channel_history 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_channel_history": {}
  }
}

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

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

FAQ

Questions about get_channel_history

What does the get_channel_history tool do? +

Get message history from a channel. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_channel_history? +

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

What risk level is get_channel_history? +

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

Can I rate-limit get_channel_history? +

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

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

get_channel_history is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp 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 →