Skip to main content
Glama
Sign In
portkey-admin-mcp

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_access_policies

Read-onlyIdempotent

Inspect active workspace access policies without changing permissions. Filter by subject, server, effect, enabled state, or creation time and return paginated policy summaries with versions.

Instructions

Inspect active workspace access policies, newest first, without changing permissions. Filter by subject, MCP server, effect, enabled state, or creation time. Returns total and the current page of policy summaries with versions; use get_access_policy for complete subjects and targets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
effectNoFilter by allow or deny effect
searchNoSearch policy names
enabledNoFilter enabled or disabled policies; false is preserved
user_idNoPolicies naming this user or matching all users
agent_idNoPolicies naming this agent or matching all agents
end_timeNoPolicies created at or before this ISO 8601 timestamp
page_sizeNoItems per page; the published API permits zero
server_idNoPolicies targeting this MCP server ID
created_byNoFilter by creator user ID
start_timeNoPolicies created at or after this ISO 8601 timestamp
current_pageNoZero-based page number; the first page is 0
workspace_idNoWorkspace UUID or slug

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv1.0.8

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new context: results are ordered newest first, the tool changes nothing ('without changing permissions'), and returned policy summaries are partial (version summaries) requiring a follow-up call for full subjects/targets. That partial-result warning is exactly the kind of behavioral trait annotations cannot express.

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 sentences, zero filler, front-loaded with the verb and scope before the filter list and the sibling routing. Every clause carries information the agent needs.

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

Completeness5/5

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

An output schema exists and the description still helpfully signals paging ('total and the current page'), so the agent knows to paginate with page_size/current_page. With all params documented and safety covered by annotations, nothing essential is missing for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so both the semantics and constraints of all 12 parameters are already documented in the schema. The description only restates the filter categories ('subject, MCP server, effect, enabled state, or creation time') without adding syntax or edge-case meaning, so the baseline 3 applies.

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?

States a specific verb+resource ('Inspect active workspace access policies'), the ordering ('newest first'), and explicitly distinguishes itself from the detail sibling ('use get_access_policy for complete subjects and targets'). An agent can separate it from list_/get_access_policy without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent: use this for paged summaries, use get_access_policy for complete subjects and targets. It also enumerates the filter dimensions that select a subset. It stops short of stating prerequisites or a true 'when not to use' case, so it lands just below the top.

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