getting_started · Astria-Index MCP: Risk & Policy

WHAT IT DOES

What getting_started does on Astria-Index

AI agents use getting_started to create or update resources in Astria-Index — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Astria-Index environment.

WHY IT NEEDS A POLICY

Why getting_started needs a policy

An AI agent can call getting_started faster than any human can review — one bad instruction and it creates or modifies resources in Astria-Index by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

getting_started Rate-limited

getting_started stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getting_started": {
      "limits": [
        {
          "counter": "getting_started_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Astria-Index, so you can run agents against it safely.

FAQ

Questions about getting_started

What does the getting_started tool do? +

getting_started. It is categorised as a Write tool in the Astria-Index MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on getting_started? +

Register the Astria-Index MCP server in PolicyLayer and add a rule for getting_started: 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 Astria-Index. Nothing to install.

What risk level is getting_started? +

getting_started is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit getting_started? +

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

How do I block getting_started completely? +

Set action: deny in the PolicyLayer 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.

What MCP server provides getting_started? +

getting_started is provided by the Astria-Index MCP server (pl-odin/astria-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.