send_log · Otel MCP: Risk & Policy

WHAT IT DOES

What send_log does on Otel

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

WHY IT NEEDS A POLICY

Why send_log needs a policy

Sending log records modifies the state of the observability backend by creating new log entries. This is reversible (logs can be filtered, archived, or deleted) and does not execute code or delete data irreversibly. However, log injection could be used to pollute observability systems or mask malicious activity, warranting medium severity.

From the tool's definition Tool name 'send_log' and description 'Send one or more log records' indicate creation/modification of log data. The server emits telemetry data to OTLP endpoints, making this a Write operation that creates new log records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_log Rate-limited

send_log 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": {
    "send_log": {
      "limits": [
        {
          "counter": "send_log_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 Otel, so you can run agents against it safely.

FAQ

Questions about send_log

What does the send_log tool do? +

Send one or more log records. It is categorised as a Write tool in the Otel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_log? +

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

What risk level is send_log? +

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

Can I rate-limit send_log? +

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

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

send_log is provided by the Otel MCP server (probsjustin/otel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.