LOG ASSESSMENT — Record a pattern assessment for a consultation session.
AI agents use log_pattern_assessment to create or update resources in Iconsult MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconsult MCP environment.
This tool writes/records data (a pattern assessment) to a consultation session. It creates or modifies stored records reversibly. There is no indication of destructive, financial, or execution behavior. Severity is low as it only logs assessment data within a consulting context.
From the tool's definition LOG ASSESSMENT — Record a pattern assessment for a consultation session
Documented attack patterns abuse exactly the kind of access log_pattern_assessment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Iconsult MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for log_pattern_assessment:
{
"version": "1",
"default": "deny",
"tools": {
"log_pattern_assessment": {
"limits": [
{
"counter": "log_pattern_assessment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} log_pattern_assessment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
LOG ASSESSMENT — Record a pattern assessment for a consultation session. It is categorised as a Write tool in the Iconsult MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iconsult MCP server in PolicyLayer and add a rule for log_pattern_assessment: 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 Iconsult MCP. Nothing to install.
log_pattern_assessment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the log_pattern_assessment 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 log_pattern_assessment. 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.
log_pattern_assessment is provided by the Iconsult MCP server (marcus-waldman/iconsult_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Iconsult MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Iconsult MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.