revoke_report_schedule_historical_access

WHAT IT DOES

What revoke_report_schedule_historical_access does on AdButler

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

PARAMETERS

Parameter	Type	Required	Description
`schedule_id`	number	Yes	Schedule ID
`report_config_id`	number	Yes	Report configuration ID

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why revoke_report_schedule_historical_access needs a policy

Revoking access is a permission/authorization modification (write operation). It modifies access control settings reversibly (access could presumably be re-granted), so it falls under Write rather than Destructive. Misuse could deny legitimate users access to historical report data, which has a medium blast radius.

From the tool's definition 'Revoke historical access for a report schedule' — removes access rights/permissions for a report schedule

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

revoke_report_schedule_historical_access Rate-limited

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

FAQ

Questions about revoke_report_schedule_historical_access

What does the revoke_report_schedule_historical_access tool do? +

Revoke historical access for a report schedule. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does revoke_report_schedule_historical_access accept? +

revoke_report_schedule_historical_access accepts 2 parameters: schedule_id, report_config_id. Required: schedule_id, report_config_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on revoke_report_schedule_historical_access? +

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

What risk level is revoke_report_schedule_historical_access? +

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

Can I rate-limit revoke_report_schedule_historical_access? +

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

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

revoke_report_schedule_historical_access is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.