get_connection_log

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/get-connection-log.md

WHAT IT DOES

What get_connection_log does on Meridian

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

Parameter	Type	Required	Description
`limit`	integer	—	Max entries to return (default 100, max 200).
`since`	string	—	ISO timestamp (UTC). Only return events at or after this time. Example: '2026-07-15 03:00:00'

Parameters from the server's own tool schema.

RISK

Why get_connection_log is rated Low

This tool retrieves and queries historical connection logs without modifying any data. The explicit '[MAINTENANCE] Read-only' designation and the phrase 'Return the recent... log' confirm its retrieval-only nature, making it a Read action.

From the tool's definition Tool name: 'get_connection_log'; Description: 'Read-only: Return the recent /mcp connection-event log... Every HTTP /mcp request Meridian receives is recorded: timestamp, MCP method, auth_result, tools_returned, client_user_agent, and HTTP response_status.'

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_connection_log safely

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

get_connection_log Allowed

get_connection_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": {
    "get_connection_log": {}
  }
}

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

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

FAQ

Questions about get_connection_log

What does the get_connection_log tool do? +

[MAINTENANCE] Read-only: Return the recent /mcp connection-event log for this tenant (newest first, up to 200 entries). Every HTTP /mcp request Meridian receives is recorded: timestamp, MCP method (initialize/tools/list/tools/call/...), auth_result (success/oauth/no_token/invalid_token/expired), tools_returned (tool count for tools/list responses), client_user_agent, and HTTP response_status. Use this to diagnose client-side outages (zero tools returned, auth failures, unexpected User-Agents) in real time or after the fact without needing raw Fly.io log access. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does get_connection_log accept? +

get_connection_log accepts 2 parameters: limit, since. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_connection_log? +

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

What risk level is get_connection_log? +

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

Can I rate-limit get_connection_log? +

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

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

get_connection_log is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meridian, and thousands of servers like it.

This server

All 175 Meridian 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 →