Step-by-step setup checklist. Shows your registration status, whether you're logging interactions, composition completeness, and signal coverage — with the next action you should take. Call this if you're unsure where to start.
Part of the ACR — Agent Composition Records MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke getting_started to trigger processes or run actions in ACR — Agent Composition Records. 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.
getting_started can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept 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.
tools:
getting_started:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full ACR — Agent Composition Records policy for all 25 tools.
Agents calling execute-class tools like getting_started have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
getting_started is one of the high-risk operations in ACR — Agent Composition Records. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Step-by-step setup checklist. Shows your registration status, whether you're logging interactions, composition completeness, and signal coverage — with the next action you should take. Call this if you're unsure where to start.. It is categorised as a Execute tool in the ACR — Agent Composition Records MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for getting_started. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the ACR — Agent Composition Records MCP server.
getting_started 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 getting_started rule in your Intercept 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 Intercept policy for getting_started. 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.
getting_started is provided by the ACR — Agent Composition Records MCP server (@tethral/acr-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept