Low Risk

log_event_user

log_event_user

How to control log_event_user ↓

What log_event_user does on FortiOS 7 6 X MCP Server

AI agents call log_event_user to retrieve information from FortiOS 7 6 X MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why log_event_user needs a policy

The tool name strongly implies reading/retrieving user event logs from FortiOS. No creation, modification, deletion, or execution semantics are apparent from the name. However, confidence is lowered due to the empty description. Log access could reveal sensitive security events, justifying medium severity rather than low.

From the tool's definition Tool name 'log_event_user' suggests querying user event logs. The 'log' prefix indicates data retrieval. Description is empty, reducing confidence.

Documented attack patterns abuse exactly the kind of access log_event_user gives an agent:

How to control log_event_user

PolicyLayer is an MCP gateway — it sits between your AI agents and FortiOS 7 6 X MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for log_event_user:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_event_user": {}
  }
}

log_event_user is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register FortiOS 7 6 X MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about log_event_user

What does the log_event_user tool do? +

log_event_user. It is categorised as a Read tool in the FortiOS 7 6 X MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on log_event_user? +

Register the FortiOS 7 6 X MCP Server MCP server in PolicyLayer and add a rule for log_event_user: 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 FortiOS 7 6 X MCP Server. Nothing to install.

What risk level is log_event_user? +

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

Can I rate-limit log_event_user? +

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

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

log_event_user is provided by the FortiOS 7 6 X MCP Server MCP server (paoloamato2/fortinet-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every FortiOS 7 6 X MCP Server tool call.

Start from FortiOS 7 6 X MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

240 FortiOS 7 6 X MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.