AI agents call get_project_files to retrieve information from Penpot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries project file information without any side effects. It fits the Read category (list, get, fetch). The severity is low because accessing file metadata poses minimal risk—no data is modified, deleted, or executed. The confidence is high because the description clearly indicates a retrieval operation.
From the tool's definition Tool name and description indicate retrieval of files: 'Get files for a specific project'. No modification, deletion, or execution occurs; this is a read-only query operation.
Documented attack patterns abuse exactly the kind of access get_project_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Penpot MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_files:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_files": {}
}
}get_project_files is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get files for a specific project. It is categorised as a Read tool in the Penpot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Penpot MCP Server MCP server in PolicyLayer and add a rule for get_project_files: 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 Penpot MCP Server. Nothing to install.
get_project_files 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 get_project_files 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 get_project_files. 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.
get_project_files is provided by the Penpot MCP Server MCP server (montevive/penpot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Penpot MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Penpot MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.