Get full workspace context in one call: user ID, team ID, all spaces with boards and lists. Use this first instead of calling get_my_account + get_spaces + get_board_details separately.
AI agents call get_context to retrieve information from Superthread Mcp Extended without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing workspace metadata and structural information. The description explicitly frames it as a replacement for multiple read operations (get_my_account + get_spaces + get_board_details), confirming it performs only data retrieval with no state changes.
From the tool's definition Tool name 'get_context' and description 'Get full workspace context in one call' indicates retrieval of data (user ID, team ID, spaces, boards, lists) with no modification or side effects.
Attacks that exploit this kind of access
Get full workspace context in one call: user ID, team ID, all spaces with boards and lists. Use this first instead of calling get_my_account + get_spaces + get_board_details separately. It is categorised as a Read tool in the Superthread Mcp Extended MCP Server, which means it retrieves data without modifying state.
Register the Superthread Mcp Extended MCP server in PolicyLayer and add a rule for get_context: 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 Superthread Mcp Extended. Nothing to install.
get_context 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 get_context 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 get_context. 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.
get_context is provided by the Superthread Mcp Extended MCP server (jaey-p/superthread-mcp-extended). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →