opencontext.archaeology.search
Full-text search across Open Context 200,000+ published archaeological records, including excavated objects (pottery, tools, bones, coins), site contexts (trenches, rooms, floors), media (photographs, 3D models, drawings), and field documents. Returns paginated list of matching items with label, ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opencontext.archaeology.search.md
What opencontext.archaeology.search does on Apibase
AI agents call opencontext.archaeology.search 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 |
|---|---|---|---|
rows | integer | — | Number of results to return per page (1–50, default 10). |
query | string | Yes | Full-text search query for archaeological items (e.g. "Roman pottery", "Bronze Age burial", "Petra temple", "obsidian flake"). Searches labels, descriptions, an |
start | integer | — | Zero-based pagination offset. Use with rows to page through results (e.g. start=10, rows=10 to get the second page). |
item_type | string | — | Filter by item category. "subjects" for excavated objects and contexts (default); "media" for images, 3D models, and videos; "documents" for field notes and rep |
Parameters from the server's own tool schema.
Why opencontext.archaeology.search is rated Low
Read-only search returning published archaeological data with no side effects.
From the tool's definition Full-text search across Open Context 200,000+ published archaeological records
Attacks that exploit this kind of access
The rule that runs opencontext.archaeology.search 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 opencontext.archaeology.search, this is the rule to start with:
opencontext.archaeology.search 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 opencontext.archaeology.search call is checked against it from then on.
Questions about opencontext.archaeology.search
Full-text search across Open Context 200,000+ published archaeological records, including excavated objects (pottery, tools, bones, coins), site contexts (trenches, rooms, floors), media (photographs, 3D models, drawings), and field documents. Returns paginated list of matching items with label, URI, excavation project, geographic context (site → region hierarchy), latitude/longitude, date range (BCE/CE), item category, and a text snippet. Filter by item type (subjects/media/documents) or search all at once. Data is CC BY 4.0 from 220+ published excavation projects worldwide, maintained by the Alexandria Archive Institute. Response includes items per page and start offset for pagination. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
opencontext.archaeology.search accepts 4 parameters: rows, query, start, item_type. Required: query. 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 opencontext.archaeology.search: 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.
opencontext.archaeology.search 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 opencontext.archaeology.search 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 opencontext.archaeology.search. 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.
opencontext.archaeology.search 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