# retrieveIdentityProviderByTypeWithId

Retrieves one or more identity provider for the given type. For types such as Google, Facebook, Twitter and LinkedIn, only a single identity provider can exist. For types such as OpenID Connect and SAMLv2 more than one identity provider can be configured so this request may return multiple identity providers.

Agent View of the PolicyLayer registry record for `retrieveIdentityProviderByTypeWithId`. HTML page: https://policylayer.com/tools/io-fusionauth-mcp-api/retrieveidentityproviderbytypewithid

## Facts

- Tool: `retrieveIdentityProviderByTypeWithId`
- Server: Fusionauth (`@fusionauth/mcp-api`) — https://policylayer.com/tools/io-fusionauth-mcp-api.md
- Install: `npx -y @fusionauth/mcp-api`
- Homepage: https://github.com/FusionAuth/fusionauth-mcp-api
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

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

## Why retrieveIdentityProviderByTypeWithId is rated Low

The tool retrieves identity provider configurations by type. It has no side effects, does not modify data, and does not trigger external actions. This is a straightforward data retrieval operation. Severity is low because exposing identity provider configurations could leak metadata, but the data itself is typically non-sensitive configuration that an authenticated user might legitimately access.

From the tool's own definition: "Tool description uses 'Retrieves' and 'return multiple identity providers' — this is purely a query operation that fetches configuration data without modification."

## Use case

AI agents call retrieveIdentityProviderByTypeWithId to retrieve information from Fusionauth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Fusionauth:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "retrieveIdentityProviderByTypeWithId": {}
  }
}
```

## Other tools on Fusionauth (313)

- `deleteAPIKeyWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteapikeywithid.md
- `deleteApplicationRoleWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteapplicationrolewithid.md
- `deleteApplicationWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteapplicationwithid.md
- `deleteConnectorWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteconnectorwithid.md
- `deleteConsentWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteconsentwithid.md
- `deleteEmailTemplateWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteemailtemplatewithid.md
- `deleteEntityGrantWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteentitygrantwithid.md
- `deleteEntityTypePermissionWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteentitytypepermissionwithid.md
- `deleteEntityTypeWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteentitytypewithid.md
- `deleteEntityWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteentitywithid.md
- `deleteFormFieldWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteformfieldwithid.md
- `deleteFormWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteformwithid.md
- `deleteGroupMembersWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletegroupmemberswithid.md
- `deleteGroupWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletegroupwithid.md
- `deleteIdentityProviderWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteidentityproviderwithid.md
- `deleteIPAccessControlListWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteipaccesscontrollistwithid.md
- `deleteJwtRefresh` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletejwtrefresh.md
- `deleteKeyWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletekeywithid.md
- `deleteLambdaWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletelambdawithid.md
- `deleteMessageTemplateWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletemessagetemplatewithid.md
- `deleteMessengerWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletemessengerwithid.md
- `deleteOAuthScopeWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteoauthscopewithid.md
- `deleteTenantWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletetenantwithid.md
- `deleteThemeWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletethemewithid.md
- `deleteUserActionReasonWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuseractionreasonwithid.md
- `deleteUserActionWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuseractionwithid.md
- `deleteUserBulk` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuserbulk.md
- `deleteUserLinkWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuserlinkwithid.md
- `deleteUserRegistrationWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuserregistrationwithid.md
- `deleteUserTwoFactorWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteusertwofactorwithid.md
- …and 283 more: https://policylayer.com/tools/io-fusionauth-mcp-api.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-fusionauth-mcp-api · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-fusionauth-mcp-api