get_context

Pull full state snapshot for a project — tasks, blockers, decisions, SOPs, environment.

Server Studio Catharsis Universal Project Coordinator MCP studio-catharsis-creative-lab/project_com_mcp
Category Read
Risk class Low
Parameters 00 required

What get_context does on Studio Catharsis Universal Project Coordinator MCP

AI agents call get_context to retrieve information from Studio Catharsis Universal Project Coordinator MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_context needs a policy

This tool retrieves and queries existing project coordination data with no side effects. It does not create, modify, delete, execute code, or commit financial obligations. Although it may expose sensitive project state information (medium data sensitivity), the blast radius of misuse is limited to information disclosure rather than destructive or operational harm. Classified as Read with low severity.

From the tool's definition Tool name 'get_context' and description 'Pull full state snapshot' indicate retrieval of project state without modification. The verb 'pull' and noun 'snapshot' denote read-only querying of tasks, blockers, decisions, SOPs, and environment data.

Questions about get_context

What does the get_context tool do? +

Pull full state snapshot for a project — tasks, blockers, decisions, SOPs, environment. It is categorised as a Read tool in the Studio Catharsis Universal Project Coordinator MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_context? +

Register the Studio Catharsis Universal Project Coordinator 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 Studio Catharsis Universal Project Coordinator MCP. Nothing to install.

What risk level is get_context? +

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

Can I rate-limit get_context? +

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.

How do I block get_context completely? +

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.

What MCP server provides get_context? +

get_context is provided by the Studio Catharsis Universal Project Coordinator MCP server (studio-catharsis-creative-lab/project_com_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.