get_projects

Returns a list of project identifiers (browser origin URLs) that have recorded render data.

SERVERWhy Did You Render SOURCE0x1f320/why-did-you-render-mcp

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/0x1f320-why-did-you-render-mcp/get-projects.md

WHAT IT DOES

What get_projects does on Why Did You Render

AI agents call get_projects to retrieve information from Why Did You Render without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_projects is rated Low

This tool retrieves or queries project identifiers from stored render data. It performs a simple list/get operation that has no side effects, does not modify data, execute code, delete anything, or move money. It is clearly a Read operation with low severity since it only exposes project metadata (browser origin URLs) without enabling any consequential actions.

From the tool's definition Tool name is 'get_projects' and description states it 'Returns a list of project identifiers'. The verb 'Returns' and the read-only nature of listing project identifiers without modification indicates data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_projects safely

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

get_projects Allowed

get_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": {
    "get_projects": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Why Did You Render, apply this rule, and every get_projects call is checked against it from then on.

FAQ

Questions about get_projects

What does the get_projects tool do? +

Returns a list of project identifiers (browser origin URLs) that have recorded render data. It is categorised as a Read tool in the Why Did You Render MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_projects? +

Register the Why Did You Render MCP server in PolicyLayer and add a rule for get_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 Why Did You Render. Nothing to install.

What risk level is get_projects? +

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

Can I rate-limit get_projects? +

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

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

get_projects is provided by the Why Did You Render MCP server (0x1f320/why-did-you-render-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Why Did You Render, and thousands of servers like it.

This server

All 14 Why Did You Render tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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