Skip to main content
Glama
Sign In
PingOne Advanced Identity Cloud MCP Server

PingOne Advanced Identity Cloud MCP Server

Official
by pingidentity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create CORS Policy

createCorsPolicy

Creates a new CORS policy by specifying all required fields (origins, methods, headers, etc.) and returns the policy ID.

Instructions

Create a new CORS policy on the global AM CorsService. All seven policy fields are required. A user-facing policyId may optionally be supplied; if omitted, AM assigns one. The policy ID is returned in the success response.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "acceptedOrigins": "<acceptedOrigins>",
      "acceptedMethods": "<acceptedMethods>",
      "acceptedHeaders": "<acceptedHeaders>",
      "exposedHeaders": "<exposedHeaders>",
      "maxAge": "<maxAge>",
      "allowCredentials": "<allowCredentials>",
      "enabled": "<enabled>"
    },
    "name": "createCorsPolicy"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxAgeYesPreflight cache duration in seconds
enabledYesWhether the policy is enabled; if false, no CORS headers are added
policyIdNoOptional user-facing identifier for the CORS policy. If omitted, AM assigns one.
exposedHeadersYesResponse headers exposed to the browser
acceptedHeadersYesNon-simple request headers allowed during preflight
acceptedMethodsYesHTTP methods allowed during preflight
acceptedOriginsYesAllowed origins (e.g. ["https://example.org"])
allowCredentialsYesWhether to send Access-Control-Allow-Credentials: true on responses

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Disclosure that all seven fields are required and policyId optional adds value beyond annotations. Returns policy ID. Does not contradict annotations; provides useful behavioral context.

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

Conciseness5/5

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

Three concise sentences, front-loaded with purpose, no redundancy.

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

Completeness4/5

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

Covers creation process, required fields, optional policyId, and return value. Could mention global scope more explicitly, but adequate for an agent.

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

Parameters4/5

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

Schema coverage is 100% but description summarizes required fields, optional policyId, and return value, adding context beyond schema descriptions.

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

Purpose5/5

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

Clear verb 'Create' and specific resource 'CORS policy on the global AM CorsService' distinguish it from sibling create tools like createJourney or createManagedObject.

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

Usage Guidelines3/5

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

Describes creation context but lacks explicit guidance on when to use this tool vs alternatives like updateCorsPolicy or deleteCorsPolicy. No conditions or exclusions mentioned.

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

Deploy Server

Other Tools