henry_getConfig

Read credential status and the real Foundry model catalog (GET /v1/henry/config) [service status: not_deployed]

SERVERGenesis SOURCE@lifesi/genesis-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lifesi-genesis-mcp/henry-getconfig.md

WHAT IT DOES

What henry_getConfig does on Genesis

AI agents call henry_getConfig to retrieve information from Genesis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why henry_getConfig is rated Low

Even though henry_getConfig only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs henry_getConfig safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For henry_getConfig, this is the rule to start with:

henry_getConfig Allowed

henry_getConfig 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": {
    "henry_getConfig": {}
  }
}

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

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

FAQ

Questions about henry_getConfig

What does the henry_getConfig tool do? +

Read credential status and the real Foundry model catalog (GET /v1/henry/config) [service status: not_deployed]. It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on henry_getConfig? +

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

What risk level is henry_getConfig? +

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

Can I rate-limit henry_getConfig? +

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

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

henry_getConfig is provided by the Genesis MCP server (@lifesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Genesis, and thousands of servers like it.

This server

All 252 Genesis tools →

Across the catalogue

The MCP Attack Database →

Guides

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