convert_time_period_to_epoch_ms · NewRelic MCP Server MCP

WHAT IT DOES

What convert_time_period_to_epoch_ms does on NewRelic MCP Server

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

WHY IT NEEDS A POLICY

Why convert_time_period_to_epoch_ms needs a policy

An AI agent can call convert_time_period_to_epoch_ms faster than any human can review — one bad instruction and it creates or modifies resources in NewRelic MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

convert_time_period_to_epoch_ms Rate-limited

convert_time_period_to_epoch_ms 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": {
    "convert_time_period_to_epoch_ms": {
      "limits": [
        {
          "counter": "convert_time_period_to_epoch_ms_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 NewRelic MCP Server, so you can run agents against it safely.

FAQ

Questions about convert_time_period_to_epoch_ms

What does the convert_time_period_to_epoch_ms tool do? +

Convert human-readable time strings to epoch milliseconds. Supports relative times like. It is categorised as a Write tool in the NewRelic MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on convert_time_period_to_epoch_ms? +

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

What risk level is convert_time_period_to_epoch_ms? +

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

Can I rate-limit convert_time_period_to_epoch_ms? +

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

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

convert_time_period_to_epoch_ms is provided by the NewRelic MCP Server MCP server (ruminaider/newrelic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.