get-astro-config

// WHEN AI AGENTS USE THIS TOOL

AI agents call get-astro-config to retrieve information from Astro without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON GET-ASTRO-CONFIG

Even though get-astro-config only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

astro.yaml

tools:
  get-astro-config:
    rules:
      - action: allow

See the full Astro policy for all 8 tools.

// DETAILS

Tool Name get-astro-config

Category Read

MCP Server Astro MCP Server

Risk Level Low

// MORE ASTRO TOOLS

Read get-astro-changes Read get-astro-integration Read get-astro-server-address Read list-astro-integrations Read list-astro-routes Read Parameters Read search-astro-docs

// WHAT CAN GO WRONG

Agents calling read-class tools like get-astro-config have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the get-astro-config tool do? +

Get the Astro config object containing comprehensive project settings including file paths (root, src, public, output directories), site URL, build options, server settings, enabled integrations, markdown processing configuration, image handling, Vite plugins, security settings, and experimental features. It is categorised as a Read tool in the Astro MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-astro-config? +

Add a rule in your Intercept YAML policy under the tools section for get-astro-config. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Astro MCP server.

What risk level is get-astro-config? +

get-astro-config is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-astro-config? +

Yes. Add a rate_limit block to the get-astro-config 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.

How do I block get-astro-config completely? +

Set action: deny in the Intercept policy for get-astro-config. 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.

What MCP server provides get-astro-config? +

get-astro-config is provided by the Astro MCP server (astro-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Astro