Medium Risk

wikidata_resolve_external_id

Look up a Wikidata entity by an external identifier such as a DOI, PubMed ID, ORCID iD, or OpenAlex ID. Returns match=<entity> on success, match=null when not found, and match=null with multipleMatches populated when a Wikidata data integrity issue causes more than one entity to claim the same ex...

Part of the Wikidata Mcp Server server.

wikidata_resolve_external_id can modify Wikidata Mcp Server data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE WIKIDATA MCP SERVER →

Free to start. No card required.

AI agents use wikidata_resolve_external_id to create or modify resources in Wikidata Mcp Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call wikidata_resolve_external_id repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Wikidata Mcp Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "wikidata_resolve_external_id": {
      "limits": [
        {
          "counter": "wikidata_resolve_external_id_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Wikidata Mcp Server policy for all 7 tools.

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

ENFORCE ON MY WIKIDATA MCP SERVER →

These attack patterns abuse exactly the kind of access wikidata_resolve_external_id 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 wikidata_resolve_external_id only ever does what you allow.

SECURE WIKIDATA MCP SERVER →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the wikidata_resolve_external_id tool do? +

Look up a Wikidata entity by an external identifier such as a DOI, PubMed ID, ORCID iD, or OpenAlex ID. Returns match=<entity> on success, match=null when not found, and match=null with multipleMatches populated when a Wikidata data integrity issue causes more than one entity to claim the same external ID. Common cross-server join use cases: CrossRef DOI → Wikidata paper QID (P356), PubMed PMID → Wikidata paper QID (P698), ORCID → author QID (P496), OpenAlex ID → entity QID (P10283). Known value normalization is applied automatically: DOIs are uppercased, PMID prefixes stripped, ORCID hyphens normalized.. It is categorised as a Write tool in the Wikidata Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wikidata_resolve_external_id? +

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

What risk level is wikidata_resolve_external_id? +

wikidata_resolve_external_id is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wikidata_resolve_external_id? +

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

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

wikidata_resolve_external_id is provided by the Wikidata Mcp Server MCP server (@cyanheads/wikidata-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Wikidata Mcp Server tool call.

Deterministic rules across all 7 Wikidata Mcp Server 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.