replicate_list_predictions
List recent predictions for a Replicate account.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/replicate-list-predictions.md
What replicate_list_predictions does on UnClick
AI agents call replicate_list_predictions 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 |
|---|---|---|---|
cursor | string | — | |
api_token | string | Yes |
Parameters from the server's own tool schema.
Why replicate_list_predictions is rated Low
This is a read-only operation that queries historical prediction data from a Replicate account. It does not create, modify, delete, or execute any operations; it merely retrieves and displays existing information. The blast radius of misuse is minimal—an attacker gains visibility into past predictions but cannot alter account state or trigger new computations.
From the tool's definition Tool name and description indicate listing/querying 'recent predictions for a Replicate account' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs replicate_list_predictions 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 replicate_list_predictions, this is the rule to start with:
replicate_list_predictions 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 replicate_list_predictions call is checked against it from then on.
Questions about replicate_list_predictions
List recent predictions for a Replicate account. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
replicate_list_predictions accepts 2 parameters: cursor, api_token. Required: api_token. 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 replicate_list_predictions: 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.
replicate_list_predictions 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 replicate_list_predictions 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 replicate_list_predictions. 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.
replicate_list_predictions is provided by the UnClick MCP server (@unclick/mcp-server). 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