Find troubleshooting solutions and related issues for Microsoft 365 agents and apps development. Searches across Agents Toolkit, Teams SDK, Teams Samples, and documentation repositories. Use this tool when encountering errors, unexpected behaviors, or implementation challenges.
AI agents call troubleshoot to retrieve information from M365agentstoolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
question | string | Yes | Description of the issue or error you're experiencing |
Parameters from the server's own tool schema.
This tool retrieves and searches existing troubleshooting documentation and issues across multiple repositories. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is purely informational—a read-only search operation over development documentation and known issues.
From the tool's definition Tool description states it 'Searches across' documentation and repositories and 'Find[s] troubleshooting solutions and related issues'. The verb 'find' and 'search' indicate query/retrieval operations with no data modification.
Attacks that exploit this kind of access
Find troubleshooting solutions and related issues for Microsoft 365 agents and apps development. Searches across Agents Toolkit, Teams SDK, Teams Samples, and documentation repositories. Use this tool when encountering errors, unexpected behaviors, or implementation challenges. It is categorised as a Read tool in the M365agentstoolkit MCP Server, which means it retrieves data without modifying state.
troubleshoot accepts 1 parameter: question. Required: question. The full parameter table on this page comes from the server's own tool schema.
Register the M365agentstoolkit MCP server in PolicyLayer and add a rule for troubleshoot: 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 M365agentstoolkit. Nothing to install.
troubleshoot 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 troubleshoot 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 troubleshoot. 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.
troubleshoot is provided by the M365agentstoolkit MCP server (@microsoft/m365agentstoolkit-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 →