resolve_date_range · TrendRadar MCP: Risk & Policy

WHAT IT DOES

What resolve_date_range does on TrendRadar

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

WHY IT NEEDS A POLICY

Why resolve_date_range needs a policy

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_date_range Rate-limited

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

FAQ

Questions about resolve_date_range

What does the resolve_date_range tool do? +

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

How do I enforce a policy on resolve_date_range? +

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

What risk level is resolve_date_range? +

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

Can I rate-limit resolve_date_range? +

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

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

resolve_date_range is provided by the TrendRadar MCP server (xhh-im/trendradar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.