This record as markdown: /tools/3ilm-mcp/get-pattern-details.md
What get_pattern_details does on 3ilm
AI agents call get_pattern_details to retrieve information from 3ilm without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
pattern | string | Yes | Exact pattern name (kebab-case). One of: fee-miscalculation, dos-griefing, reentrancy, trusted-actor, overflow, staleness, rounding, access-control, oracle-mani |
Parameters from the server's own tool schema.
Why get_pattern_details is rated Low
The tool retrieves or queries data about patterns (presumably security patterns or vulnerability patterns) with no indication of side effects, modification, or execution capabilities. No description was provided, which slightly lowers confidence, but the naming convention and sibling tools strongly suggest informational/read-only functionality.
From the tool's definition Tool name is 'get_pattern_details' and sibling tools are 'list_patterns' and 'search_vulnerabilities', indicating this server is a vulnerability/security pattern information system.
Attacks that exploit this kind of access
The rule that runs get_pattern_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 3ilm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_pattern_details, this is the rule to start with:
get_pattern_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 3ilm, apply this rule, and every get_pattern_details call is checked against it from then on.
Questions about get_pattern_details
get_pattern_details is a read tool on the 3ilm MCP server. It is categorised as a Read tool in the 3ilm MCP Server, which means it retrieves data without modifying state.
get_pattern_details accepts 1 parameter: pattern. Required: pattern. The full parameter table on this page comes from the server's own tool schema.
Register the 3ilm MCP server in PolicyLayer and add a rule for get_pattern_details: 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 3ilm. Nothing to install.
get_pattern_details 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_pattern_details 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_pattern_details. 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_pattern_details is provided by the 3ilm MCP server (3ilm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 3ilm, and thousands of servers like it.
This server
Across the catalogue