searchEventLogsWithId

Searches the event logs with the specified criteria and pagination.

SERVERFusionauth SOURCE@fusionauth/mcp-api

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-fusionauth-mcp-api/searcheventlogswithid.md

WHAT IT DOES

What searchEventLogsWithId does on Fusionauth

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

RISK

Why searchEventLogsWithId is rated Low

The tool performs a search operation on event logs, which is a read-only action that retrieves existing data for inspection purposes. No data is created, modified, deleted, or executed as a side effect. Searching logs has minimal blast radius as it only exposes information already present in the system.

From the tool's definition Tool name "searchEventLogsWithId" and description "Searches the event logs with the specified criteria and pagination" indicate a query/search operation that retrieves log data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs searchEventLogsWithId safely

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

searchEventLogsWithId Allowed

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

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

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

FAQ

Questions about searchEventLogsWithId

What does the searchEventLogsWithId tool do? +

Searches the event logs with the specified criteria and pagination. It is categorised as a Read tool in the Fusionauth MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on searchEventLogsWithId? +

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

What risk level is searchEventLogsWithId? +

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

Can I rate-limit searchEventLogsWithId? +

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

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

searchEventLogsWithId is provided by the Fusionauth MCP server (@fusionauth/mcp-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Fusionauth, and thousands of servers like it.

This server

All 314 Fusionauth tools →

Across the catalogue

The MCP Attack Database →

Guides

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