forbidden

What happened

The MCP request was refused because of who it acts as. There are two reasons:

• The key named another user in the x-fullvision-acting-user header, and only the workspace's own dashboard key may act on behalf of someone else. Message: "This API key cannot act on behalf of another user."
• The acting user is not a member of the workspace. Message: "The acting user is not a member of this workspace."

Why it usually happens

• The key was created by someone who has since left the workspace. A key acts as the person who created it, so it stops working when they leave.
• A key other than the workspace's own dashboard key sent x-fullvision-acting-user naming someone else.

How to fix

• Use an API key created by a current member of the workspace.
• Do not send the x-fullvision-acting-user header.

Envelope

{
  "error": {
    "code": "forbidden",
    "message": "The acting user is not a member of this workspace.",
    "param": null,
    "doc_url": "https://docs.fullvision.io/errors/forbidden",
    "trace_id": "tr_01HXYZ..."
  }
}