Get rule details from the Colorado Code of Regulations.
AI agents call get_rule to retrieve information from Umbrella Terminal MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static rule details from a public regulatory database. It performs a query operation with no side effects—no data is created, modified, deleted, or executed. The context (Colorado legislative intelligence) and sibling tools (all query-oriented: batch_get_entities, get_bill, get_bill_history, etc.) confirm this is a read-only data retrieval function.
From the tool's definition Tool name 'get_rule' with description 'Get rule details from the Colorado Code of Regulations' indicates retrieval of publicly available regulatory information with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get rule details from the Colorado Code of Regulations. It is categorised as a Read tool in the Umbrella Terminal MCP MCP Server, which means it retrieves data without modifying state.
Register the Umbrella Terminal MCP server in PolicyLayer and add a rule for get_rule: 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 Umbrella Terminal MCP. Nothing to install.
get_rule 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 get_rule 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 get_rule. 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.
get_rule is provided by the Umbrella Terminal MCP server (theblackcompany/umbrella_terminal_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 →