search_activities
Search for activities (e.g. development, meetings, vacation). Use this to find activity IDs for logging hours.
This record as markdown: /tools/adriantr-tripletex-mcp/search-activities.md
What search_activities does on Tripletex MCP Server
AI agents call search_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.
Why search_activities is rated Low
The tool performs a query/search operation to retrieve activity information and IDs. It has no capability to modify, create, delete, or execute operations. This is a straightforward read operation typical of search functionality in accounting systems.
From the tool's definition Tool description explicitly states 'Search for activities' and 'find activity IDs' - these are retrieval operations with no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs search_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 search_activities, this is the rule to start with:
search_activities 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 search_activities call is checked against it from then on.
Questions about search_activities
Search for activities (e.g. development, meetings, vacation). Use this to find activity IDs for logging hours. 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 search_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.
search_activities 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 search_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.
Set action: deny in the PolicyLayer policy for search_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.
search_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.
More on Tripletex MCP Server, and thousands of servers like it.
This server
Across the catalogue