Medium Risk

set_workspace

Set or change the workspace directory. Re-indexes the codebase at the new path.

How to control set_workspace ↓

What set_workspace does on Astrograph

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

Medium Risk

Why set_workspace needs a policy

The tool modifies the active workspace configuration (Write category) rather than executing arbitrary operations or destructively deleting data. Re-indexing is reversible by switching to a different workspace. Severity is medium because changing the workspace could affect downstream analysis results and agent behavior, but the change itself is not destructive and can be undone by setting a different path.

From the tool's definition Tool description states 'Set or change the workspace directory. Re-indexes the codebase at the new path.' — this modifies workspace state and triggers re-indexing, a reversible configuration change.

Documented attack patterns abuse exactly the kind of access set_workspace gives an agent:

How to control set_workspace

PolicyLayer is an MCP gateway — it sits between your AI agents and Astrograph, and nothing reaches the server without passing your rules. This is the rule we recommend for set_workspace:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_workspace": {
      "limits": [
        {
          "counter": "set_workspace_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

set_workspace 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.

  1. Create a free account and register Astrograph — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about set_workspace

What does the set_workspace tool do? +

Set or change the workspace directory. Re-indexes the codebase at the new path. It is categorised as a Write tool in the Astrograph MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_workspace? +

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

What risk level is set_workspace? +

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

Can I rate-limit set_workspace? +

Yes. Add a rate_limit block to the set_workspace 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 set_workspace completely? +

Set action: deny in the PolicyLayer policy for set_workspace. 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 set_workspace? +

set_workspace is provided by the Astrograph MCP server (thaylo/astrograph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Astrograph tool call.

Start from Astrograph, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

12 Astrograph tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.