Get the help section exposed by SentinelX capabilities.
AI agents call sentinel_help to retrieve information from SentinelX Core MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves help documentation from SentinelX Core, which is a passive query operation with no side effects. It does not create, modify, delete, execute code, move money, or trigger external operations. The blast radius of misuse is minimal—an AI could only access help text, which is typically non-sensitive documentation intended for public visibility.
From the tool's definition Tool name 'sentinel_help' and description 'Get the help section exposed by SentinelX capabilities' indicate a read-only operation that retrieves documentation or help information without modifying state or executing code.
Attacks that exploit this kind of access
Get the help section exposed by SentinelX capabilities. It is categorised as a Read tool in the SentinelX Core MCP MCP Server, which means it retrieves data without modifying state.
Register the SentinelX Core MCP server in PolicyLayer and add a rule for sentinel_help: 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 SentinelX Core MCP. Nothing to install.
sentinel_help is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sentinel_help 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.
Set action: deny in the PolicyLayer policy for sentinel_help. 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.
sentinel_help is provided by the SentinelX Core MCP server (pensados/sentinelx-core-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →