Microsoft Active Directory MCP Server

Overview Schema Source Related Servers Discussions Admin

ad_get_security_group_changes

Track security group changes by querying Active Directory logs for recent modifications within a configurable time window, supporting audit and change review.

Instructions

[Security & Audit] [READ] Consultar alteracoes em grupos de seguranca nos logs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ad_get_security_group_changes"
  }
}

Input Schema

Name	Required	Description	Default
`hours`	No
`limit`	No
`correlation_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

C2.6/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden, yet it only asserts [READ]. It says nothing about which domain controllers' logs are queried, whether results are aggregated or per-DC, whether the query is expensive, or how results are capped. The read-only claim is the only behavioral signal offered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tagged sentence with no wasted words, but it is under-specified rather than concise: the tags are front-loaded and useful, yet the payload sentence is too thin for a three-parameter audit tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so return values needn't be described, but with no annotations and 0% schema coverage the description should explain the time-window semantics, result capping, and the correlation_id. It also switches to Portuguese while the tool name is English, adding a small comprehension cost.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description mentions none of the three parameters. 'hours' and 'limit' are semi-self-explanatory by name (time window, result cap), but 'correlation_id' is entirely opaque — neither schema nor description explains its purpose or format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: querying changes to security groups in logs, tagged [Security & Audit] [READ]. This is clearly distinguishable from siblings like ad_list_groups (current state) or ad_generate_security_audit_report (report generation). It stops short of 5 because it doesn't specify the log source or scope, leaving the agent to infer what 'logs' means.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance and no named alternative. The [Security & Audit] tag implies an audit context, but the agent receives no cue about when to prefer this over ad_list_groups, ad_get_group, or ad_generate_security_audit_report.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server