custom_date_comparison · AdminAgent MCP: Risk & Policy

WHAT IT DOES

What custom_date_comparison does on AdminAgent

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

WHY IT NEEDS A POLICY

Why custom_date_comparison needs a policy

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_date_comparison Rate-limited

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

FAQ

Questions about custom_date_comparison

What does the custom_date_comparison tool do? +

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

How do I enforce a policy on custom_date_comparison? +

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

What risk level is custom_date_comparison? +

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

Can I rate-limit custom_date_comparison? +

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

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

custom_date_comparison is provided by the AdminAgent MCP server (rushikeshmore/admin-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.