Dash0 Raises $110M Series B at $1B Valuation

Last updated: July 5, 2026

Agent0 Doesn't Call Expected Tools

Why Agent0 skips or can't access certain tools and how to fix it.

When Agent0 doesn't call the tools you expect, the issue is usually with tool access permissions, prompt clarity, or integration setup.

Agent0 Doesn't Post to Slack

Symptom: Automation runs but doesn't post to Slack channels.

Common causes:

Slack Tool Not Allowed (Most Common)

Check:

  • Go to Guardrails > Allowed Tools
  • Is the list empty (default policy) or does it include slack:* or slack:slackSendMessage?

Fix for default policy:

  • Default policy only allows Slack posting when trigger is from Slack
  • For schedule or check triggers, explicitly allow slack:slackSendMessage

Fix for custom allowed tools:

  • Add slack:* to allow all Slack tools
  • Or add slack:slackSendMessage specifically

Note: Slack connector tools work under any Network Access setting (No Network or Full Network). They do not require Full Network access.

Prompt Doesn't Say Where to Post

Check your prompt:

  • Does it say "Post to #incidents" or similar?
  • Or does it just say "analyze the data"?

Fix:

123
Query error rate for service {{label.service}}.


Post your findings to #incidents with recommended actions.

Be explicit about the output destination.

Slack Integration Not Connected

Check:

  • Go to Settings > Integrations
  • Is Slack shown as "Connected"?

Fix:

  • Connect the Slack integration
  • Follow the OAuth flow
  • Verify bot has access to target channels

Agent0 Doesn't Query Metrics

Symptom: Agent0 responds from knowledge without querying actual data.

Common causes:

Prompt Too Vague

Problem:

1
Tell me about service health.

Fix:

1
Query the error rate and p99 latency for service {{label.service}} over the last hour. Show the actual numbers from Dash0.

Query Tool Not Required

Agent0 might skip queries if not explicitly required.

Fix:

  • Go to Guardrails > Required Tool Calls
  • Add getMetricQuery or relevant query tool
  • Agent0 will retry if it skips the query

Default Tool Policy Blocking Queries

This is rare (Dash0 query tools are almost always allowed), but check:

Fix:

  • Go to Guardrails > Allowed Tools
  • Ensure dash0:* is included or list is empty (default policy)

Agent0 Skips GitHub/Linear Actions

Symptom: Doesn't comment on PRs or create Linear tickets.

Important: GitHub and Linear connectors are read-only:

  • GitHub connector: Provides only githubListRepos tool
  • Linear connector: Read-only, no write tools available
  • PR comments: Require Full Network access + gh CLI via bash (not a connector tool)
  • Linear tickets: Cannot be created via automation (no write tool exists)

To Comment on GitHub PRs

Requirements:

  1. Set Network Access to Full Network in guardrails
  2. Use gh CLI commands via bash tool, not GitHub connector tools
  3. Ensure prompt explicitly instructs to use bash commands

Example prompt:

1234
Analyze the PR for potential issues.


If you find concerns, use bash to run:
gh pr comment <pr-number> --body "Your analysis here"

GitHub Integration (Read-Only)

What it provides:

  • githubListRepos tool to list accessible repositories
  • No write capabilities

Check:

  • Go to Settings > Integrations
  • Is GitHub connected?

Fix:

  • Connect the integration for read access
  • For write operations (PR comments), use gh CLI with Full Network

Linear Integration (Read-Only)

What it provides:

  • Read-only access to Linear issues
  • No ticket creation or commenting tools

Workaround:

  • Post findings to Slack instead
  • Use webhooks to external systems if Linear ticket creation is required

Tool Denied in Manage Tools Dialog

If you previously denied a tool, it won't be accessible even if the namespace is allowed.

Check:

  1. Go to Guardrails > Allowed Tools
  2. Click Manage Tools
  3. Search for the tool
  4. Check if status is Denied

Fix:

  • Change status from Denied to Allowed
  • Or remove it from the denied list

Debugging Tool Access Issues

Systematic approach:

1. Check Run History

  • Open the run that didn't call the tool
  • Look at which tools were actually called
  • Check for tool call errors or failures

2. Verify Tool Is Available

Test if tool is accessible:

  • Create a minimal test automation
  • Simple prompt: "Call [tool name] to check if it works"
  • If this fails, the issue is permissions/integration
  • If this works, the issue is in your complex prompt

3. Review Guardrails

Checklist:

  • ✓ Network access appropriate for the tool
  • ✓ Tool included in allowed tools (or list is empty for default)
  • ✓ Tool not denied in Manage Tools dialog
  • ✓ Integration connected (for Slack/GitHub/Linear)

4. Make Prompt More Explicit

Before:

1
Check the service.

After:

1234
1. Query error rate for service {{label.service}} using getMetricQuery
2. Post your findings to #incidents using slackSendMessage


Both steps are required.

Common Scenarios

Schedule Wants to Post to Slack

Problem: Default policy blocks Slack posting from schedule triggers.

Fix:

  • Add slack:slackSendMessage to Allowed Tools
  • Or add slack:* to allow all Slack actions

Slack Message Wants to Query and Post

Default behavior: Works automatically (default policy allows both).

If it doesn't work:

  • Ensure prompt explicitly says to query and post
  • Check Slack integration is connected

Failed Check Wants to Comment on GitHub

Problem: GitHub connector is read-only; PR comments require gh CLI.

Fix:

  • Set Network Access to Full Network
  • Use bash tool with gh CLI commands
  • Make prompt explicit: "Use bash to run gh pr comment..."

Further Reading