ALWAYS call this first. Verifies license tier and which ad platforms are connected. Shows what is available based on your plan (Starter/Pro/Premium/Elite). Use this before any other tool.
AI agents call check_setup to retrieve information from Agent1st Ads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
check_setup retrieves and displays configuration and entitlement information without modifying, executing, or deleting anything. This is a classic Read operation. The low severity reflects that misuse (e.g., checking setup repeatedly) poses minimal risk to the ad accounts or data themselves.
From the tool's definition Tool description states it 'Verifies license tier and which ad platforms are connected. Shows what is available' — purely informational queries with no side effects.
Attacks that exploit this kind of access
ALWAYS call this first. Verifies license tier and which ad platforms are connected. Shows what is available based on your plan (Starter/Pro/Premium/Elite). Use this before any other tool. It is categorised as a Read tool in the Agent1st Ads MCP Server, which means it retrieves data without modifying state.
Register the Agent1st Ads MCP server in PolicyLayer and add a rule for check_setup: 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 Agent1st Ads. Nothing to install.
check_setup is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_setup 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.
Set action: deny in the PolicyLayer policy for check_setup. 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.
check_setup is provided by the Agent1st Ads MCP server (nolas-shadow/agent1st-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
check_setup is one line of Agent1st Ads's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →