Low Risk

translate_identifiers

Translate research output identifiers (DOIs, PMIDs, arXiv IDs, etc.) into Altmetric IDs. Useful for discovering which identifiers Altmetric has data for. Supports batch translation of up to 100,000 identifiers per request. The identifier type is auto-detected. This is a commercial feature requiri...

Part of the Altmetric server.

translate_identifiers is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE ALTMETRIC →

Free to start. No card required.

AI agents call translate_identifiers to retrieve information from Altmetric without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though translate_identifiers only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "translate_identifiers": {}
  }
}

See the full Altmetric policy for all 11 tools.

Get this rule live on your own Altmetric server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ALTMETRIC →

View all 11 tools →

These attack patterns abuse exactly the kind of access translate_identifiers gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so translate_identifiers only ever does what you allow.

SECURE ALTMETRIC →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the translate_identifiers tool do? +

Translate research output identifiers (DOIs, PMIDs, arXiv IDs, etc.) into Altmetric IDs. Useful for discovering which identifiers Altmetric has data for. Supports batch translation of up to 100,000 identifiers per request. The identifier type is auto-detected. This is a commercial feature requiring a paid API key.. It is categorised as a Read tool in the Altmetric MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on translate_identifiers? +

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

What risk level is translate_identifiers? +

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

Can I rate-limit translate_identifiers? +

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

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

translate_identifiers is provided by the Altmetric MCP server (altmetric/altmetric-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Altmetric tool call.

Deterministic rules across all 11 Altmetric tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.