list_projects
List projects with their client, type, budget, and dates, optionally filtered to active-only. Answers "what projects am I working on?"
This record as markdown: /tools/com-getsavitools-savi-tools/list-projects.md
What list_projects does on Savi Tools
AI agents call list_projects to retrieve information from Savi Tools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
active | boolean | — | Filter to active (true) or paused (false) projects. Omit for all. |
Parameters from the server's own tool schema.
Why list_projects is rated Low
This tool queries and returns project data without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security risk—the worst-case scenario is exposure of project metadata (names, clients, budgets, dates), which is informational rather than directly harmful.
From the tool's definition The tool 'list_projects' retrieves project information (client, type, budget, dates) with optional filtering.
Attacks that exploit this kind of access
The rule that runs list_projects safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Savi Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_projects, this is the rule to start with:
list_projects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Savi Tools, apply this rule, and every list_projects call is checked against it from then on.
Questions about list_projects
List projects with their client, type, budget, and dates, optionally filtered to active-only. Answers "what projects am I working on?". It is categorised as a Read tool in the Savi Tools MCP Server, which means it retrieves data without modifying state.
list_projects accepts 1 parameter: active. The full parameter table on this page comes from the server's own tool schema.
Register the Savi Tools MCP server in PolicyLayer and add a rule for 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 Savi Tools. Nothing to install.
list_projects 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 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.
Set action: deny in the PolicyLayer policy for 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.
list_projects is provided by the Savi Tools MCP server (https://getsavitools.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Savi Tools, and thousands of servers like it.
This server
Across the catalogue