manage_cross_tenant_access

WHAT IT DOES

What manage_cross_tenant_access does on Microsoft 365 Core MCP Server

AI agents use manage_cross_tenant_access to create or update resources in Microsoft 365 Core MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Microsoft 365 Core MCP Server environment.

WHY IT NEEDS A POLICY

Why manage_cross_tenant_access needs a policy

This tool modifies trust relationships and partner access configurations across Azure AD/Microsoft 365 tenants. While it could potentially have severe consequences if misconfigured (affecting organizational security boundaries), the operations are reversible—trust settings and partner configurations can be updated or reverted. This places it in the Write category rather than Destructive.

From the tool's definition Tool name 'manage_cross_tenant_access' combined with description stating it manages 'inbound/outbound trust settings and partner configurations' indicates creation or modification of access control policies and B2B collaboration settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_cross_tenant_access Rate-limited

manage_cross_tenant_access 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_cross_tenant_access": {
      "limits": [
        {
          "counter": "manage_cross_tenant_access_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Microsoft 365 Core MCP Server, so you can run agents against it safely.

FAQ

Questions about manage_cross_tenant_access

What does the manage_cross_tenant_access tool do? +

Manage cross-tenant access settings for B2B collaboration, including inbound/outbound trust settings and partner configurations. It is categorised as a Write tool in the Microsoft 365 Core MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_cross_tenant_access? +

Register the Microsoft 365 Core MCP Server MCP server in PolicyLayer and add a rule for manage_cross_tenant_access: 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 Microsoft 365 Core MCP Server. Nothing to install.

What risk level is manage_cross_tenant_access? +

manage_cross_tenant_access is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage_cross_tenant_access? +

Yes. Add a rate_limit block to the manage_cross_tenant_access 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.

How do I block manage_cross_tenant_access completely? +

Set action: deny in the PolicyLayer policy for manage_cross_tenant_access. 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.

What MCP server provides manage_cross_tenant_access? +

manage_cross_tenant_access is provided by the Microsoft 365 Core MCP Server MCP server (roycedamien/m365-core-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.