Managed servicesCommand contributionv1.0.0Built-in coverage

Elasticsearch command protection

Reviews explicit DELETE requests to recognizable Elasticsearch API targets.

Claim publisher pageView exact source Documentation

Evidence at a glance

Source
Merged native coverage · f440ae1a9f
Activation
This coverage is built into the native Guard runtime.
Maintainer
Project maintained
Coverage
1 rules · 1 permissions

Coverage and limits

Reviews explicit DELETE requests to recognizable Elasticsearch API targets.

  • Coverage is limited to the reviewed operations and the surrounding Guard policy.
  • A maintainer profile is not a security certification or an official upstream endorsement.

Command mapping and enforcement

How Guard maps this extension onto your workspace policy: which commands it recognizes, which tools it touches, and how each tool state resolves.

1
Reviewed rules
1
Permission checks
0
Per-tool overrides
v1.0.0
Listing version

Runtime identity

Catalog ID
command.search.elasticsearch
Guard enforcement ID
command.search.elasticsearch
Source path
src/codex_plugin_scanner/guard/runtime/command_builtin_extension_registry.py

Tool state mapping

No per-tool overrides are declared. Every tool this extension touches resolves through the workspace Guard policy as-is.

Action classes

Elasticsearch destructive command

Frequently asked questions

What does Elasticsearch command protection cover?

Reviews explicit DELETE requests to recognizable Elasticsearch API targets. The listing declares 1 rule and 1 permission check. Coverage is limited to these reviewed operations and the surrounding Guard policy.

Is Elasticsearch command protection active by default?

Built-in coverage: This coverage is built into the native Guard runtime. Enabling state is always controlled through Guard policy, never from this directory.

Who maintains Elasticsearch command protection?

This listing is maintained by the HOL Guard project itself as part of the native runtime catalog.

Is a listing of Elasticsearch command protection a security guarantee?

No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.