622 tools. 342 can modify or destroy data without limits.
114 destructive tools with no built-in limits. Policy required.
Last updated:
Community server · catalogue entry verified 05/06/2026 · full schemas captured for 622 of 622 tools
Running more than one server? Check your whole stack →
Full per-tool breakdown → Model it in the token calculator →
342 of AdButler's 622 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and AdButler, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"create_contract_payment": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
} Financial tools should be explicitly enabled per use case, not open by default.
{
"campaign_bulk_delete_catalog_ad_items": {
"deny_if": [
{
"conditions": [],
"on_deny": "Blocked by default. Requires approval."
}
]
}
} Destructive tools should never be available to autonomous agents without human approval.
{
"revoke_report_schedule_historical_access": {
"limits": [
{
"counter": "revoke_report_schedule_historical_access_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"describe_adbutler_api": {
"limits": [
{
"counter": "describe_adbutler_api_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Free to start. No card required.
Other MCP servers with similar tools — same risk classification, starter policies for each.
Yes. The AdButler server exposes 1 financial tools including create_contract_payment. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.
Yes. The AdButler server exposes 113 destructive tools including campaign_bulk_delete_catalog_ad_items, cancel_signature_request, delete_advertiser. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.
The AdButler server has 225 write tools including revoke_report_schedule_historical_access, resend_signature_request, verify_trial_email. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach AdButler.
622 tools across 3 categories: Destructive, Read, Write. 280 are read-only. 342 can modify, create, or delete data.
Register the AdButler MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 622 AdButler tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
622 AdButler tools catalogued and risk-classified — across an index of 43,000+ MCP servers.