Return app/project names configured for this workspace. Risk: read.
AI agents call project_list_apps 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 metadata (app/project names) from the workspace without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal blast radius—an AI agent misusing it could only enumerate workspace applications, which poses no direct harm to data or operations.
From the tool's definition Tool description explicitly states 'Return app/project names configured for this workspace' with self-identified risk category 'read'. The verb 'Return' and noun 'names' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Return app/project names configured for this workspace. 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_list_apps: 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_list_apps 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_list_apps 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_list_apps. 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_list_apps 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 →