Retrieve configured project context. Risk: read.
AI agents call project_get_context to retrieve information from Notion MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data without side effects, reversible changes, code execution, deletion, or financial impact. It is a straightforward data retrieval operation typical of Read category tools. The explicit 'Risk: read' designation in the description further confirms this classification.
From the tool's definition Tool name 'project_get_context' and description 'Retrieve configured project context' indicate a read-only retrieval operation with no modification or execution implied. The server itself notes 'read' as the risk level for this tool.
Attacks that exploit this kind of access
Retrieve configured project context. Risk: read. It is categorised as a Read tool in the Notion MCP MCP Server, which means it retrieves data without modifying state.
Register the Notion MCP server in PolicyLayer and add a rule for project_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 Notion MCP. Nothing to install.
project_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 project_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 project_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.
project_get_context is provided by the Notion MCP server (limelight-management-group/notion-mcp). 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 →