list-reply-log

List all replies received by the chat-bridge channel (for testing two-way communication)

SERVERFrontmcp SOURCEagentfront/frontmcp

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/frontmcp/list-reply-log.md

WHAT IT DOES

What list-reply-log does on Frontmcp

AI agents call list-reply-log to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list-reply-log is rated Low

This tool queries and retrieves historical communication data from a chat-bridge channel without modifying, deleting, or executing operations. It is a read-only inspection tool intended for testing and debugging purposes. The blast radius of misuse is minimal—an agent could access chat logs but cannot alter, delete, or execute actions.

From the tool's definition 'List all replies received' indicates retrieval/query operation with no modification capability. The description explicitly frames this as a testing utility for reading chat-bridge channel history.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list-reply-log safely

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

list-reply-log Allowed

list-reply-log 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": {
    "list-reply-log": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every list-reply-log call is checked against it from then on.

FAQ

Questions about list-reply-log

What does the list-reply-log tool do? +

List all replies received by the chat-bridge channel (for testing two-way communication). It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list-reply-log? +

Register the Front MCP server in PolicyLayer and add a rule for list-reply-log: 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 Frontmcp. Nothing to install.

What risk level is list-reply-log? +

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

Can I rate-limit list-reply-log? +

Yes. Add a rate_limit block to the list-reply-log 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 list-reply-log completely? +

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

list-reply-log is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →