Koru Shield MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport mode, e.g. 3000. | |
| MCP_TRANSPORT | No | Set to "http" to enable HTTP transport (remote). | |
| KORU_SHIELD_API_KEY | Yes | Your Koru Shield API key. Required to authenticate. Can alternatively be passed per-request as an Authorization Bearer header in HTTP transport mode. | |
| KORU_SHIELD_API_URL | No | Overrides the API base URL. | https://my.korushield.com/api |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_profilesA | List all DNS protection profiles on the account (e.g. Kids, Work, IoT). |
| get_profileC | Get details of a single profile. |
| list_rulesB | List custom allow/deny rules for a profile. |
| create_ruleB | Create a custom allow or deny rule for a domain on a profile. Use kind=deny to block a domain, kind=allow to explicitly permit it. |
| delete_ruleA | Delete a custom rule from a profile. Destructive: the rule stops applying immediately. |
| list_filter_categoriesA | List filter categories (adult content, gambling, social media, etc.) and whether each is enabled on a profile. |
| set_filter_categoryC | Enable or disable a filter category on a profile. |
| simulate_policyA | Check what the profile policy would do for a domain right now: allowed, blocked, and why. Does not change anything. |
| get_logsA | Get recent DNS query logs: what was queried, allowed or blocked, and when. Useful for reviewing activity or investigating a block. |
| analytics_summaryB | Summary of DNS activity: total queries, blocked vs allowed counts, blocked percentage, IPv4/IPv6, encrypted queries. |
| list_schedulesB | List time-based schedules on a profile (e.g. bedtime 21:00-07:00 on weekdays). |
| create_scheduleC | Create a time-based schedule on a profile. Rules and filter categories can reference schedules to apply only during the window. |
| delete_scheduleA | Delete a schedule from a profile. Destructive: rules referencing it lose their time window. |
| list_devicesB | List devices enrolled on a profile and their protection status. |
| get_entitlementsA | Get the account plan, limits (max rules, profiles, devices), and current usage. |
| get_referral_codeA | Get the account referral code and link for the give-a-month-get-a-month program. |
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 16 tools
Each tool targets a distinct resource or action: profiles, rules, filter categories, schedules, logs, analytics, devices, and account info. Overlap is minimal; simulate_policy, get_logs, and analytics_summary serve different query intents. No two tools appear to do the same thing.
Nearly all tools follow a consistent verb_noun snake_case pattern (list_profiles, create_rule, set_filter_category). The only deviation is analytics_summary, which is a noun phrase rather than verb_noun. Still highly readable and predictable.
16 tools is slightly above the ideal 3–15 range but reasonable given the multiple sub-resources (profiles, rules, categories, schedules, devices, analytics, account). Each tool maps to a clear operation, with no obvious redundancy.
The surface lacks profile lifecycle operations (create/update/delete profile), rule and schedule updates, and device enrollment/removal. Only list operations exist for devices and entitlements. These gaps will force agents to work around missing CRUD for core resources.