This record as markdown: /tools/creativelead-unclick/trove-get-work.md
What trove_get_work does on UnClick
AI agents call trove_get_work to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why trove_get_work is rated Low
This tool retrieves information about a work from Trove (Australian National Library's discovery service) using an ID parameter. It is a simple data retrieval operation that does not modify, delete, or execute any external operations. The minimal blast radius and read-only nature classify it as a Read category risk with low severity.
From the tool's definition Tool name 'trove_get_work' and description 'Get a specific Trove work by ID' indicate a retrieval operation. The verb 'Get' and action of fetching data by identifier are characteristic of read-only queries with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs trove_get_work safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trove_get_work, this is the rule to start with:
trove_get_work 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 UnClick, apply this rule, and every trove_get_work call is checked against it from then on.
Questions about trove_get_work
Get a specific Trove work by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
trove_get_work accepts 2 parameters: id, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for trove_get_work: 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 UnClick. Nothing to install.
trove_get_work 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 trove_get_work 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 trove_get_work. 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.
trove_get_work is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue