opencontext.archaeology.facets

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.facets.md

WHAT IT DOES

What opencontext.archaeology.facets does on Apibase

AI agents call opencontext.archaeology.facets 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
`query`	string	Yes	Search query to compute facets for (e.g. "Roman pottery", "Bronze Age"). Use an empty string "" to get facets across the entire Open Context database.
`item_type`	string	—	Optional filter to restrict facet computation to a specific item type. "subjects" for excavated objects; "media" for images/3D; "documents" for field notes; "al

Parameters from the server's own tool schema.

RISK

Why opencontext.archaeology.facets is rated Low

Tool retrieves and aggregates query statistics without modifying, executing, or deleting any data.

From the tool's definition Retrieve aggregated facet statistics for a search query. Returns: total matched record count, query time, date range, geographic distribution.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

opencontext.archaeology.facets Allowed

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

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.facets call is checked against it from then on.

FAQ

Questions about opencontext.archaeology.facets

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

Retrieve aggregated facet statistics for a search query across Open Context without downloading individual records. Returns: total matched record count, query time, earliest and latest date range in BCE/CE across all matches, geographic distribution (continent-level facets with counts, e.g. Asia 99K, Europe 89K), item type breakdown (Subjects of Observation, Media, Documents, Projects), top matching excavation projects with counts, and linked-data description facets (Creator, License, Subject, etc.). Use this tool to quickly understand the scope and geographic/temporal distribution of archaeological records matching a query before retrieving individual items with opencontext.archaeology.search. Pass an empty string to get global database statistics. 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.facets accept? +

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

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

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

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

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

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

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

opencontext.archaeology.facets 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 →