wikimedia-commons.media.random
Get a random sample of Wikimedia Commons media files (titles, page IDs, and description-page URLs). Useful for discovery, sampling, or "surprise me" style prompts. Data: commons.wikimedia.org (MediaWiki Action API), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wikimedia-commons.media.random.md
What wikimedia-commons.media.random does on Apibase
AI agents call wikimedia-commons.media.random to retrieve information from Apibase 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 |
|---|---|---|---|
count | integer | — | Number of random files to return (1-20, default 5) |
Parameters from the server's own tool schema.
Why wikimedia-commons.media.random is rated Low
Retrieves public media metadata without modification, deletion, or external effects.
From the tool's definition Get a random sample of Wikimedia Commons media files, no side effects.
Attacks that exploit this kind of access
The rule that runs wikimedia-commons.media.random safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wikimedia-commons.media.random, this is the rule to start with:
wikimedia-commons.media.random 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 Apibase, apply this rule, and every wikimedia-commons.media.random call is checked against it from then on.
Questions about wikimedia-commons.media.random
Get a random sample of Wikimedia Commons media files (titles, page IDs, and description-page URLs). Useful for discovery, sampling, or "surprise me" style prompts. Data: commons.wikimedia.org (MediaWiki Action API), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
wikimedia-commons.media.random accepts 1 parameter: count. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for wikimedia-commons.media.random: 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 Apibase. Nothing to install.
wikimedia-commons.media.random 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 wikimedia-commons.media.random 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 wikimedia-commons.media.random. 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.
wikimedia-commons.media.random is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue