Docs

Security

What the Sypnia MCP server can and cannot do, the one tool that writes and how to switch it off, and what to know before you connect an agent to production data.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. What the server can and cannot do
  2. The one tool that writes
  3. Make the server read-only
  4. Text from your app reaches your agent
  5. Where the data goes
  6. The token
  7. Remote or local
  8. What is logged
  9. Limits
  10. Report a problem

Engine Cloud Read this before you connect an agent to a project with real users. It says exactly what the server can do with the token you give it.

What the server can and cannot do

It canIt cannot
Read problems, their analysis, stacks, traces and releasesChange your code, your repository or your deploys. It has no access to them
Read sessions as a list of events: pages, clicks by their label, failed calls, errorsReturn what a person typed. It is never collected
Read performance numbers, uptime status, and searchReturn replay recordings or page snapshots. No tool does, with any token
Mark a problem as resolved (one tool, see below)Ignore or delete a problem, delete a session or a person’s data
Create, read or revoke keys and tokens; change settings, alert rules, webhooks or uptime checks
Open, merge or close a pull request
Reach another project. A token is one project

Nine of the ten tools only read. Reading has no side effect: asking twice changes nothing and costs nothing but a request.

The one tool that writes

resolve_problem marks a problem as resolved. It is there so the loop can close: the agent fixes the code, you merge, the agent marks the problem.

It is safe by design:

  • It is reversible. Reopen the problem at any time, in the app, the Console, the CLI or the API.
  • It undoes itself. If the failure happens again, Sypnia reopens the problem and creates an alert. A problem resolved too early cannot hide a failure that is still happening.
  • It is recorded. The problem keeps who resolved it (resolved_by: mcp:<token name>), when, and the note.
  • It is the only one. No other tool changes anything.

The tool’s own description tells the agent to call it only after the fix is merged or deployed. Most clients also ask you before a tool that writes runs.

Make the server read-only

Remote server

Add ?read_only=true to the address. The tool is then not listed at all.

Terminal
claude mcp add --transport http sypnia \
  "https://mcp.sypnia.com/mcp?read_only=true" \
  --header "Authorization: Bearer YOUR_API_TOKEN"

In a JSON configuration: "url": "https://mcp.sypnia.com/mcp?read_only=true".

Read-only here is about the MCP server. The same read token could still resolve a problem through the HTTP API, because resolving is one of the reversible marks that scope allows.

Text from your app reaches your agent

Tool results contain text that Sypnia did not write: error messages, the labels of things people clicked, page titles, names your app sent with identify(). A person using your app could put words there on purpose, hoping your agent reads them as instructions («ignore your instructions and…»).

What Sypnia does about it:

  • The server’s instructions tell the agent that this text is data and must never be followed.
  • Results are structured: such text sits in named fields (message, label, text), never mixed into the server’s own wording.
  • Strings are cut to their limits (an error message to 500 characters, a label to 80), so there is little room.
  • Nothing a person typed into a form is ever in a result.

What you should do: keep your client’s confirmation for commands and file changes switched on when the agent is working from production data, and review what it changes. This is true of any tool that brings outside text to an agent, not only of Sypnia.

Where the data goes

The server gives results to your coding agent. Your agent sends them to its model provider, under your agreement with that provider. Sypnia does not choose that model and does not see that conversation.

So what a tool returns is what leaves: code locations and source lines of your app, error messages, click labels, the ids of people, and their names and e-mails only if your app sends them with identify(). If that must not reach your agent’s provider, do not send names and e-mails to Sypnia, or use a token for a project that has none.

The token

  • Use an API token with only read. See Authentication.
  • One token per agent and per person, named after them.
  • Never an admin token, never the root token.
  • Read it from the environment; do not commit it.
  • Revoke it when a laptop is lost or a person leaves: it stops working within a minute.

Remote or local

Remote serverLocal server (@sypnia/mcp)
Who runs itSypnia (Cloud) or your engineYour machine
What it holdsNothing. Each call goes to the engine with your tokenNothing. It forwards each call to the API
What you installNothingA package from npm, MIT licence, open source
The token is inYour client’s configuration, sent over HTTPSYour environment

The local server makes no other network call than to the API address you set.

What is logged

For each tool call the engine logs: the time, the token’s id, the project, the tool’s name, whether it succeeded and how long it took. It does not log the arguments or the result. On Sypnia Cloud these logs are kept for 30 days.

Limits

  • 600 requests a minute per token, shared with any other use of that token. One tool call is one to three requests.
  • A result is at most 60,000 characters.
  • A tool call that takes longer than 30 seconds is stopped and answers an error.

Report a problem

If you find a way to make the server do something this page says it cannot, write to the address on Security practices.

Sections

Start hereWhat Sypnia is, how it works, what is open source and what is the paid cloud, and the two ways to get your first problem in plain words.ConceptsThe ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.SDKsHow your app sends data to Sypnia. One SDK for the browser, one for Node, one for Next.js, and the OpenTelemetry intake for every other backend.The agentHow Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.MCP and skillsConnect your coding agent to Sypnia so it can ask what is failing in production, read what it needs to fix it, and set Sypnia up for you.API referenceThe Sypnia HTTP API: one API for the open-source engine and for Sypnia Cloud, with every endpoint, parameter, response and error.CLI referenceThe sypnia command: how to install it, the variables it reads, what its exit codes mean, and where each command is documented.Self-hostingWhat you run when you host the Sypnia engine yourself, what you need, what it costs, and what you do not get compared with Sypnia Cloud.How the engine is builtThe whole Sypnia engine on one page, from a click in your app to the sentence your coding agent reads, with the design rules and the code that holds them.Sypnia CloudHow the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.Privacy and securityWhat Sypnia collects from your app and its users, what it never collects, how masking works, how to delete data, and how the service is protected.LicensingWhich licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.GuidesStep-by-step recipes for the common ways to use Sypnia, from apps made with AI builders and Next.js on Vercel to Supabase, source maps in CI, alert e-mails from your own engine, and moving from Sentry.ReferenceThe pages you look things up in, from the event schema and the glossary to what is planned, the changelog and the common questions.
↑↓ to move↵ to openEsc to close