set_workspace_project · Stitch MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_workspace_project does on Stitch MCP Server

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

WHY IT NEEDS A POLICY

Why set_workspace_project needs a policy

This tool creates or modifies a configuration file (.stitch-project.json) in the workspace, which is a reversible write operation. It does not execute arbitrary code, delete data, or cause financial effects. The impact is limited to storing project metadata locally, making it a Write-category tool with low severity due to its constrained scope and reversibility.

From the tool's definition Tool description states it 'Associates a Stitch project with the current workspace/folder' and stores 'project info...in .stitch-project.json in the current directory.' The verb 'Associates' and the action of creating/writing to a configuration file indicates…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_workspace_project Rate-limited

set_workspace_project 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": {
    "set_workspace_project": {
      "limits": [
        {
          "counter": "set_workspace_project_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 Stitch MCP Server, so you can run agents against it safely.

FAQ

Questions about set_workspace_project

What does the set_workspace_project tool do? +

Associates a Stitch project with the current workspace/folder. The project info is stored in .stitch-project.json in the current directory. It is categorised as a Write tool in the Stitch MCP Server 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_project? +

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

What risk level is set_workspace_project? +

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

Can I rate-limit set_workspace_project? +

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

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

set_workspace_project is provided by the Stitch MCP Server MCP server (oogleyskr/stitch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.