Low Risk

get_repo_fieldset

MANDATORY FIRST STEP: Discover ALL available fields in a NGSIEM repository.

How to control get_repo_fieldset ↓

What get_repo_fieldset does on NGSIEM MCP Server

AI agents call get_repo_fieldset to retrieve information from NGSIEM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_repo_fieldset needs a policy

This tool performs schema discovery—querying what fields exist in a repository. It is a non-destructive information retrieval operation with no side effects. It does not execute searches, modify data, or trigger external operations. The low severity reflects that misuse would at worst expose schema information, which is informational rather than damaging.

From the tool's definition Tool description states 'Discover ALL available fields in a NGSIEM repository.' The verb 'discover' and the context of field discovery indicate a schema introspection operation that retrieves metadata about available fields without modifying data or executing…

Documented attack patterns abuse exactly the kind of access get_repo_fieldset gives an agent:

How to control get_repo_fieldset

PolicyLayer is an MCP gateway — it sits between your AI agents and NGSIEM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_repo_fieldset:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_repo_fieldset": {}
  }
}

get_repo_fieldset is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register NGSIEM MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_repo_fieldset

What does the get_repo_fieldset tool do? +

MANDATORY FIRST STEP: Discover ALL available fields in a NGSIEM repository. It is categorised as a Read tool in the NGSIEM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_repo_fieldset? +

Register the NGSIEM MCP Server MCP server in PolicyLayer and add a rule for get_repo_fieldset: 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 NGSIEM MCP Server. Nothing to install.

What risk level is get_repo_fieldset? +

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

Can I rate-limit get_repo_fieldset? +

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

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

get_repo_fieldset is provided by the NGSIEM MCP Server MCP server (rodkinal/cs-ngsiem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every NGSIEM MCP Server tool call.

Start from NGSIEM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

10 NGSIEM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.