scite_check_retractions

A read tool on the Zotero MCP server.

SERVERZotero MCP SOURCEpypi:zotero-mcp-server

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/54yyyu-zotero-mcp/scite-check-retractions.md

WHAT IT DOES

What scite_check_retractions does on Zotero MCP

AI agents call scite_check_retractions to retrieve information from Zotero MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why scite_check_retractions is rated Low

This tool retrieves retraction information for research items, which is a query/lookup operation with no side effects. It fits the Read category as it queries data without modifying, executing code, deleting, or committing financial transactions. The slight confidence reduction reflects the missing description, but the tool name and server context strongly suggest informational retrieval.

From the tool's definition Tool name 'scite_check_retractions' indicates checking/querying retraction data. The server context involves search, access, and analysis of research library content with no mention of modifying or deleting items.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scite_check_retractions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Zotero MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scite_check_retractions, this is the rule to start with:

scite_check_retractions Allowed

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

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

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

FAQ

Questions about scite_check_retractions

What does the scite_check_retractions tool do? +

scite_check_retractions is a read tool on the Zotero MCP server. It is categorised as a Read tool in the Zotero MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on scite_check_retractions? +

Register the Zotero MCP server in PolicyLayer and add a rule for scite_check_retractions: 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 Zotero MCP. Nothing to install.

What risk level is scite_check_retractions? +

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

Can I rate-limit scite_check_retractions? +

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

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

scite_check_retractions is provided by the Zotero MCP server (pypi:zotero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Zotero, and thousands of servers like it.

This server

All 55 Zotero tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →