opencontext.archaeology.detail

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opencontext.archaeology.detail.md

WHAT IT DOES

What opencontext.archaeology.detail does on Apibase

AI agents call opencontext.archaeology.detail 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
`uuid`	string	Yes	UUID of the Open Context item to retrieve (e.g. "013860d8-a5c9-48fc-d695-0ab6cc7c94b0"). Obtain from opencontext.archaeology.search results (last path segment o
`item_type`	string	—	Item category for routing to the correct endpoint. "subjects" for excavated objects/finds/contexts (default); "projects" for excavation projects; "media" for im

Parameters from the server's own tool schema.

RISK

Why opencontext.archaeology.detail is rated Low

Retrieves archaeological data with no side effects or mutation capability.

From the tool's definition Retrieve full archaeological record details by UUID. Returns structured data including metadata, context path, coordinates, observations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs opencontext.archaeology.detail 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.detail, this is the rule to start with:

opencontext.archaeology.detail Allowed

opencontext.archaeology.detail 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": {
    "opencontext.archaeology.detail": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every opencontext.archaeology.detail call is checked against it from then on.

FAQ

Questions about opencontext.archaeology.detail

What does the opencontext.archaeology.detail tool do? +

Retrieve full archaeological record details for a specific Open Context item by UUID and type. Returns the complete structured data including: label, category (e.g. Pottery, Coin, Human Bone), Dublin Core metadata (title, issued date, modified date), full context path (geographic hierarchy: continent → country → site → trench → unit), latitude/longitude, temporal coverage with BCE/CE ranges and period labels, creator attribution, subject tags, project membership, license, and all project-defined observations (attributes and values recorded during excavation, such as fabric type, condition, size, vessel form, description). Obtain the UUID from the last path segment of any opencontext.archaeology.search result URI. Item types: "subjects" for excavated objects and site contexts (default), "projects" for excavation projects, "media" for images and 3D models, "documents" for field notes. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does opencontext.archaeology.detail accept? +

opencontext.archaeology.detail accepts 2 parameters: uuid, item_type. Required: uuid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on opencontext.archaeology.detail? +

Register the Apibase MCP server in PolicyLayer and add a rule for opencontext.archaeology.detail: 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.

What risk level is opencontext.archaeology.detail? +

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

Can I rate-limit opencontext.archaeology.detail? +

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

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

opencontext.archaeology.detail 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

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