get_recent_activities

Get recently used activities for a project.

SERVERTripletex MCP Server SOURCEadriantr/tripletex-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/adriantr-tripletex-mcp/get-recent-activities.md

WHAT IT DOES

What get_recent_activities does on Tripletex MCP Server

AI agents call get_recent_activities 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.

RISK

Why get_recent_activities is rated Low

This tool queries and retrieves historical activity data for a project without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that has no blast radius if misused by an AI agent—at worst, it exposes activity history that may already be accessible to authenticated users.

From the tool's definition Tool name 'get_recent_activities' and description 'Get recently used activities for a project' indicate data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_recent_activities 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_activities, this is the rule to start with:

get_recent_activities Allowed

get_recent_activities 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_recent_activities": {}
  }
}

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

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

FAQ

Questions about get_recent_activities

What does the get_recent_activities tool do? +

Get recently used activities for a project. It is categorised as a Read tool in the Tripletex MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_recent_activities? +

Register the Tripletex MCP Server MCP server in PolicyLayer and add a rule for get_recent_activities: 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.

What risk level is get_recent_activities? +

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

Can I rate-limit get_recent_activities? +

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

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

get_recent_activities 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.

KEEP EXPLORING

More on Tripletex MCP Server, and thousands of servers like it.

This server

All 31 Tripletex MCP Server 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 →