workspace_get_status
Get the status of a GTM workspace: the list of changed entities (workspaceChange)
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.
Attacks that exploit this kind of access
The rule that runs workspace_get_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For workspace_get_status, this is the rule to start with:
workspace_get_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every workspace_get_status call is checked against it from then on.
Questions about workspace_get_status
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.
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.
workspace_get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
This server
Across the catalogue