codex_list_projects

List all projects in the organization

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/codex-list-projects.md

WHAT IT DOES

What codex_list_projects does on Sage MCP

AI agents call codex_list_projects to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why codex_list_projects is rated Low

This tool retrieves and enumerates projects within an organization with no side effects. It is a straightforward read operation. Severity is low because listing projects is informational; the blast radius of misuse is limited to information disclosure of project metadata, which typically has low impact in organizational contexts.

From the tool's definition Tool name 'codex_list_projects' and description 'List all projects in the organization' indicate a query operation that retrieves data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs codex_list_projects safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For codex_list_projects, this is the rule to start with:

codex_list_projects Allowed

codex_list_projects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "codex_list_projects": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every codex_list_projects call is checked against it from then on.

FAQ

Questions about codex_list_projects

What does the codex_list_projects tool do? +

List all projects in the organization. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on codex_list_projects? +

Register the Sage MCP server in PolicyLayer and add a rule for codex_list_projects: 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 Sage MCP. Nothing to install.

What risk level is codex_list_projects? +

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

Can I rate-limit codex_list_projects? +

Yes. Add a rate_limit block to the codex_list_projects 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 codex_list_projects completely? +

Set action: deny in the PolicyLayer policy for codex_list_projects. 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 codex_list_projects? +

codex_list_projects is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →