Start here when building an application. Returns an overview of what the AdCritter platform offers and a catalog of feature guides you can query with the adcritter_guidance tool to learn how to build each part of the app. Call adcritter_guidance(key) for any feature area to get detailed building ...
Part of the AdCritter for Builders server.
Free to start. No card required.
AI agents invoke adcritter_build_app to trigger processes or run actions in AdCritter for Builders. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
adcritter_build_app can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"adcritter_build_app": {
"limits": [
{
"counter": "adcritter_build_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full AdCritter for Builders policy for all 7 tools.
These attack patterns abuse exactly the kind of access adcritter_build_app gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Start here when building an application. Returns an overview of what the AdCritter platform offers and a catalog of feature guides you can query with the adcritter_guidance tool to learn how to build each part of the app. Call adcritter_guidance(key) for any feature area to get detailed building instructions with API endpoints and response shapes.. It is categorised as a Execute tool in the AdCritter for Builders MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AdCritter for Builders MCP server in PolicyLayer and add a rule for adcritter_build_app: 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 AdCritter for Builders. Nothing to install.
adcritter_build_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adcritter_build_app 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 adcritter_build_app. 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.
adcritter_build_app is provided by the AdCritter for Builders MCP server (https://mcp.adcritter.com/mcp/dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 AdCritter for Builders tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.