register_log_source · MCP Log Analyzer MCP: Risk & Policy

WHAT IT DOES

What register_log_source does on MCP Log Analyzer

AI agents use register_log_source to create or update resources in MCP Log Analyzer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Log Analyzer environment.

WHY IT NEEDS A POLICY

Why register_log_source needs a policy

This tool creates or modifies a configuration entry for a log source, which is reversible (can be unregistered or updated). It fits the Write category rather than Read (does not just retrieve) or Execute (does not run arbitrary code).

From the tool's definition Tool name 'register_log_source' with verb 'register' indicates creation or modification of a log source configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_log_source Rate-limited

register_log_source stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "register_log_source": {
      "limits": [
        {
          "counter": "register_log_source_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Log Analyzer, so you can run agents against it safely.

FAQ

Questions about register_log_source

What does the register_log_source tool do? +

register_log_source. It is categorised as a Write tool in the MCP Log Analyzer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on register_log_source? +

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

What risk level is register_log_source? +

register_log_source is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit register_log_source? +

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

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

register_log_source is provided by the MCP Log Analyzer MCP server (sedwardstx/demomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.