opencontext.archaeology.projects

SERVERApibase SOURCEapibase-mcp-client

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What opencontext.archaeology.projects does on Apibase

AI agents use opencontext.archaeology.projects to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.

Parameter	Type	Required	Description
`rows`	integer	—	Number of project results to return (1–50, default 10).
`query`	string	Yes	Search query for archaeological excavation projects or collections (e.g. "Turkey", "Roman", "DINAA", "Petra"). Use an empty string "" to browse all available pr
`start`	integer	—	Zero-based pagination offset for browsing large result sets (default 0).

Parameters from the server's own tool schema.

RISK

Why opencontext.archaeology.projects is rated Medium

An AI agent can call opencontext.archaeology.projects faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

opencontext.archaeology.projects Rate-limited

opencontext.archaeology.projects stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "opencontext.archaeology.projects": {
      "limits": [
        {
          "counter": "opencontext.archaeology.projects_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about opencontext.archaeology.projects

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

Search for archaeological excavation projects and collections published in Open Context. Returns a paginated list of matching projects with label, URI, publication date, and last update date. Each project represents a distinct archaeological investigation — from major multi-season excavations (e.g. Petra Great Temple Excavations, Murlo, Kenan Tepe) to regional surveys (e.g. Eastern Korinthia Archaeological Survey) and collaborative datasets (e.g. Digital Index of North American Archaeology — DINAA). Use the returned URI path segment as the UUID in opencontext.archaeology.detail (with item_type="projects") to retrieve full project metadata including description, geographic coverage, contributors, and linked data. Combine with opencontext.archaeology.search to find specific item types within a known project (not yet supported via API — use facets for project-based counts). It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does opencontext.archaeology.projects accept? +

opencontext.archaeology.projects accepts 3 parameters: rows, query, start. 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.projects? +

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

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

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

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

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

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

Govern customer-ops agents →Argument validation →Scoped token →