get_server_logs

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 50 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-server-logs.md

WHAT IT DOES

What get_server_logs does on Meridian

AI agents call get_server_logs 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 500).
`since`	string	—	ISO timestamp (UTC). Only return entries at or after this time. Example: '2026-07-15 03:00:00'
`seek_to`	string	—	b241a437: Positional seek hint. ISO timestamp (UTC) of the point you want to navigate to. When provided (and since= is absent), the checkpoint index supplies a
`level_filter`	string	—	Filter to a specific log level. Omit to return all WARNING-and-above entries.
`module_filter`	string	—	Substring match against the logger name (e.g. 'meridian.server', 'hosted'). Omit for no filter.

Parameters from the server's own tool schema.

RISK

Why get_server_logs is rated Low

This tool purely retrieves historical log records for diagnostic purposes with no ability to write, delete, execute code, or trigger state changes. The read-only constraint and diagnostic intent place it squarely in the Read category with low severity—logs are typically non-sensitive operational data, and misuse would only expose system information rather than cause operational harm.

From the tool's definition Tool name contains '[MAINTENANCE]' and 'Read-only' prefix. Description explicitly states 'Return recent application-level WARNING/ERROR/EXCEPTION log records' with no modification capability. Only retrieves diagnostic logging data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_server_logs 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_server_logs, this is the rule to start with:

get_server_logs Allowed

get_server_logs 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_server_logs": {}
  }
}

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_server_logs call is checked against it from then on.

FAQ

Questions about get_server_logs

What does the get_server_logs tool do? +

[MAINTENANCE] Read-only: Return recent application-level WARNING/ERROR/EXCEPTION log records (newest first, up to 500 entries). Captures any logging.warning() / logging.error() / unhandled-exception records emitted anywhere in the Meridian process — not just /mcp request metadata. Use this to diagnose server-side errors (OAuth flow failures, tools/list timeouts, deploy health issues, DB connection errors) without needing raw Fly.io log access. Complements get_connection_log (which covers per-request /mcp metadata only). Returns {count, since, level_filter, module_filter, entries}. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does get_server_logs accept? +

get_server_logs accepts 5 parameters: limit, since, seek_to, level_filter, module_filter. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_server_logs? +

Register the Meridian MCP server in PolicyLayer and add a rule for get_server_logs: 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_server_logs? +

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

Can I rate-limit get_server_logs? +

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

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

get_server_logs 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 →