get_recent_projects
Get recently used projects for timesheet entries.
This record as markdown: /tools/adriantr-tripletex-mcp/get-recent-projects.md
What get_recent_projects does on Tripletex MCP Server
AI agents call get_recent_projects to retrieve information from Tripletex MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_recent_projects is rated Low
This tool retrieves a list of recently used projects without creating, modifying, deleting, or executing any operations. It is a simple query operation that returns read-only data to help populate project selections for timesheet entries. The minimal blast radius if misused would be limited to exposure of project metadata already accessible to the authenticated user.
From the tool's definition Tool name 'get_recent_projects' and description 'Get recently used projects for timesheet entries' indicate data retrieval with the verb 'Get' and no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_recent_projects safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tripletex MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_recent_projects, this is the rule to start with:
get_recent_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 Tripletex MCP Server, apply this rule, and every get_recent_projects call is checked against it from then on.
Questions about get_recent_projects
Get recently used projects for timesheet entries. It is categorised as a Read tool in the Tripletex MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tripletex MCP Server MCP server in PolicyLayer and add a rule for get_recent_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 Tripletex MCP Server. Nothing to install.
get_recent_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 get_recent_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 get_recent_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.
get_recent_projects is provided by the Tripletex MCP Server MCP server (adriantr/tripletex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tripletex MCP Server, and thousands of servers like it.
This server
Across the catalogue