New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

workspace_get_status

Get the status of a GTM workspace: the list of changed entities (workspaceChange)

SERVERSamarth Gtm Mcp SOURCEsamarth-gtm-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/workspace-get-status.md

What workspace_get_status does on Samarth Gtm Mcp

AI agents call workspace_get_status to retrieve information from Samarth Gtm Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why workspace_get_status is rated Low

This tool queries and retrieves workspace state information (changed entities and status) without creating, modifying, deleting, or executing operations. It is a pure data retrieval operation, consistent with the server's read-only design. Low severity because exposure of workspace change history poses minimal risk compared to tools that could modify GTM configurations or financial systems.

From the tool's definition Tool returns 'the list of changed entities' and 'status'—retrieval operations with no modification capability. Described as part of a 'read-only by default' server.

Questions about workspace_get_status

What does the workspace_get_status tool do? +

Get the status of a GTM workspace: the list of changed entities (workspaceChange). It is categorised as a Read tool in the Samarth Gtm Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on workspace_get_status? +

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

What risk level is workspace_get_status? +

workspace_get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit workspace_get_status? +

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

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

workspace_get_status is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Samarth Gtm, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Samarth Gtm's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.