Id of the mcp server to add policy
Add mcp server policy
Precedence of this policy among the policies on the same MCP server. 0 is the highest rank, ascending from there (0 beats 1 beats 2...); an absent order means "no order" and ranks below every ordered policy. Orders are retained regardless of the server's policyOrderingEnabled flag but only take effect at checkout when it is true. When more than one policy grants the same tool, checkout uses the credential providers of the highest-ranked (lowest order) policy. An order must be unique among the server's policies -- updating a policy to an order another policy on that server already holds is rejected with 409. On create the order is assigned automatically (when ordering is enabled), so create does not reject on order.
The tools on this MCP server the policy grants, and the credential providers handed out when one of them is checked out.
Names of the MCP server tools this policy grants. An empty array grants every tool on the server, including tools added to it later. Explicit names grant only those tools. Omitting the field is a no-op, not an empty array. On create the policy grants no tools; on update it keeps the tools it already has. Reads are faithful to the grant: a policy saved with an empty array is returned with an empty array, and a policy that grants no tools is returned with no tools list. The policy never stores a synthetic "*" -- the wildcard is materialized only in the policy-evaluation cache.
Credential providers used at checkout for the granted tools. Only id is read on write; name is populated on read. Omitting the field is a no-op: on create nothing is stored, and on update the policy keeps the providers it already has. Send an empty array to clear them.
policy got created successfully
Precedence of this policy among the policies on the same MCP server. 0 is the highest rank, ascending from there (0 beats 1 beats 2...); an absent order means "no order" and ranks below every ordered policy. Orders are retained regardless of the server's policyOrderingEnabled flag but only take effect at checkout when it is true. When more than one policy grants the same tool, checkout uses the credential providers of the highest-ranked (lowest order) policy. An order must be unique among the server's policies -- updating a policy to an order another policy on that server already holds is rejected with 409. On create the order is assigned automatically (when ordering is enabled), so create does not reject on order.
The tools on this MCP server the policy grants, and the credential providers handed out when one of them is checked out.
Names of the MCP server tools this policy grants. An empty array grants every tool on the server, including tools added to it later. Explicit names grant only those tools. Omitting the field is a no-op, not an empty array. On create the policy grants no tools; on update it keeps the tools it already has. Reads are faithful to the grant: a policy saved with an empty array is returned with an empty array, and a policy that grants no tools is returned with no tools list. The policy never stores a synthetic "*" -- the wildcard is materialized only in the policy-evaluation cache.
Credential providers used at checkout for the granted tools. Only id is read on write; name is populated on read. Omitting the field is a no-op: on create nothing is stored, and on update the policy keeps the providers it already has. Send an empty array to clear them.
Not Found