log_daily_metrics · Revenue Engine MCP: Risk & Policy

WHAT IT DOES

What log_daily_metrics does on Revenue Engine MCP

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

WHY IT NEEDS A POLICY

Why log_daily_metrics needs a policy

This tool writes daily activity metrics to the system (likely Google Sheets based on server context). It creates or updates records reversibly, with no indication of deletion or financial transactions. Misuse could corrupt business metrics data, hence medium severity.

From the tool's definition "Log daily activity metrics" — logging/recording data is a write operation that creates or updates records

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_daily_metrics Rate-limited

log_daily_metrics 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": {
    "log_daily_metrics": {
      "limits": [
        {
          "counter": "log_daily_metrics_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 Revenue Engine MCP, so you can run agents against it safely.

FAQ

Questions about log_daily_metrics

What does the log_daily_metrics tool do? +

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

How do I enforce a policy on log_daily_metrics? +

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

What risk level is log_daily_metrics? +

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

Can I rate-limit log_daily_metrics? +

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

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

log_daily_metrics is provided by the Revenue Engine MCP server (promptishoperations/mcpspec). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.