// MCP TOOL REFERENCE

GITSCRUM STUDIO TOOLS

4 tools from the Gitscrum Studio MCP Server, categorised by risk level.

// ALL 4 GITSCRUM STUDIO TOOLS

READ 1 tools

Read auth_status Check authentication status.

WRITE 2 tools

Write auth_complete Complete login after browser authorization. Write auth_login Start login. Returns URL and code for browser authorization.

DESTRUCTIVE 1 tools

Destructive auth_logout Logout and clear token.

// RUNNING THIS SERVER

The managed route: connect Gitscrum Studio through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y @gitscrum-studio/mcp-server

// FAQ

How many tools does the Gitscrum Studio MCP server have? +

The Gitscrum Studio MCP server exposes 4 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Gitscrum Studio tools? +

Route the Gitscrum Studio server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Gitscrum Studio tools fall into? +

Gitscrum Studio tools are categorised as Read (1), Write (2), Destructive (1). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.