Risk Rule Mining MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RRM_DATA_DIR | No | Directory where data and the database live. Defaults to ./data. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesB | List loaded tables with row and column counts. |
| describe_tableC | Columns, types, primary key and foreign keys of one table. |
| profile_tableB | Column-by-column profile: role, description, nulls, distinct values, ranges, top values. |
| get_metadataC | What each table is (description, grain, size, key) and how tables relate, with coverage. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools target mostly distinct metadata layers: table inventory, table schema, column profiling, and semantic/table-relationship metadata. There is minor overlap between get_metadata and list_tables/describe_table around table keys and descriptions, but the boundaries are reasonably clear from the descriptions.
All tool names use snake_case with a leading verb and noun object: list_tables, describe_table, profile_table, get_metadata. The pattern is predictable and consistent throughout.
Four tools is a compact, focused set for metadata discovery, and each tool covers a different exploration step. However, relative to a server named Risk Rule Mining, the set is somewhat thin because it only addresses metadata preparation.
The surface only supports table discovery, schema inspection, profiling, and metadata lookup. For a Risk Rule Mining server, there are no tools to mine, evaluate, save, or manage risk rules, leaving the core domain lifecycle unaddressed.