cdp_check_sso_state

GET /sso/state?user={username}&tenant={tenant}

SERVERCDP MCP Server SOURCEatharva-joshi77/cdp-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/atharva-joshi77-cdp-mcp/cdp-check-sso-state.md

WHAT IT DOES

What cdp_check_sso_state does on CDP MCP Server

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

RISK

Why cdp_check_sso_state is rated Low

This is a Read operation as it retrieves SSO state information without side effects. Severity is medium rather than low because SSO state information could reveal user authentication status and tenant associations, which has moderate sensitivity and could inform unauthorized access attempts if an agent queries arbitrary user/tenant combinations.

From the tool's definition Tool name 'cdp_check_sso_state' and HTTP method 'GET' indicate a read operation that queries single sign-on state for a user and tenant.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cdp_check_sso_state safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CDP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cdp_check_sso_state, this is the rule to start with:

cdp_check_sso_state Allowed

cdp_check_sso_state is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cdp_check_sso_state": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CDP MCP Server, apply this rule, and every cdp_check_sso_state call is checked against it from then on.

FAQ

Questions about cdp_check_sso_state

What does the cdp_check_sso_state tool do? +

GET /sso/state?user={username}&tenant={tenant}. It is categorised as a Read tool in the CDP MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cdp_check_sso_state? +

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

What risk level is cdp_check_sso_state? +

cdp_check_sso_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cdp_check_sso_state? +

Yes. Add a rate_limit block to the cdp_check_sso_state 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 cdp_check_sso_state completely? +

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

cdp_check_sso_state is provided by the CDP MCP Server MCP server (atharva-joshi77/cdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CDP MCP Server, and thousands of servers like it.

This server

All 288 CDP MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →