search_ai_log

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 120 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/search-ai-log.md

WHAT IT DOES

What search_ai_log does on Meridian

AI agents call search_ai_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	—	Default 50, capped at 500.
`cursor`	integer	—	Offset into the ordered result set. Pass a prior response's next_cursor. Default 0.
`actor_id`	string	—
`tenant_id`	string	—
`actor_kind`	string	—	One of: session, system, human, tool, model.
`event_type`	string	—
`project_id`	string	—
`session_id`	string	—
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given.
`correlation_id`	string	—
`parent_event_id`	string	—
`since_occurred_at`	string	—	ISO-8601 UTC datetime, inclusive lower bound on occurred_at.

Parameters from the server's own tool schema.

RISK

Why search_ai_log is rated Low

Even though search_ai_log only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHigh parameter count (13 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

search_ai_log Allowed

search_ai_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": {
    "search_ai_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 search_ai_log call is checked against it from then on.

FAQ

Questions about search_ai_log

What does the search_ai_log tool do? +

[MAINTENANCE] d26b9943 (R2-B) — Read-only: EXACT-MATCH scoped search over ai_log_events, bounded and cursor-paginated. Every filter is a plain SQL equality (session_id/tenant_id/correlation_id/parent_event_id/actor_kind/actor_id/event_type) or an inclusive occurred_at range (since_occurred_at/until_occurred_at) — there is no lexical (FTS) or semantic index anywhere in this codebase yet, so the response's index_status field always honestly reports 'exact_only', never a fabricated 'complete'/'resolving' state. Filters are AND-ed together (more filters only ever narrow the result). Ordered newest-recorded-first (recorded_at DESC, id DESC — same contract as list_events), with a stable integer OFFSET cursor (pass a prior response's next_cursor back in — same contract as get_project_notes_page). Returns {project_id, filters, events, total_count, has_more, next_cursor, index_status}. limit defaults to 50, capped at 500. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does search_ai_log accept? +

search_ai_log accepts 12 parameters: limit, cursor, actor_id, tenant_id, actor_kind, event_type, project_id, session_id, project_name, correlation_id, parent_event_id, since_occurred_at. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on search_ai_log? +

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

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

Can I rate-limit search_ai_log? +

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

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

search_ai_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 235 Meridian tools →

Across the catalogue

evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

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