Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ASQAV_API_KEYYesYour Asqav API key used for authentication.
ASQAV_API_URLNoThe Asqav API URL (optional, defaults to https://api.asqav.com).https://api.asqav.com

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_policyA

Check if an action is allowed by the organization's policies.

Args:
    action_type: The action to check (e.g. "data:read:users", "api:external:call")
    agent_id: Optional agent ID to check policies for
preflight_checkA

Combined agent-status + policy-allowed check; returns CLEARED / NOT CLEARED summary.

Fail-open: a per-check exception is recorded as a warning, not a blocker.

Args:
    agent_id: The agent ID to check
    action_type: The action to check (e.g. "data:read", "api:call")
sign_actionA

Create a signed audit record for an AI agent action.

Args:
    agent_id: The agent performing the action
    action_type: Type of action (e.g. "data:read", "api:call")
    action_id: Unique identifier for this action
    payload: Optional JSON payload describing the action details
    compliance_mode: When True, mint a Compliance Receipt by sending the
        hash-only wire envelope (hash + hash_algo + payload_size). Requires
        payload to be supplied so the cloud can resolve the payload_digest
        object form.
list_agentsA

List all registered AI agents in the organization.

get_agentB

Get details for a specific AI agent.

Args:
    agent_id: The agent ID to look up
verify_signatureC

Verify an existing signature by signature_id.

Args:
    signature_id: The signature ID to verify
verify_outputA

Verify a signature and confirm the signed payload's output_hash matches expected_output.

Use to detect post-sign tampering of an agent's reported result.

Args:
    signature_id: The signature ID (from complete_action or sign_action)
    expected_output: The output string to verify against the signed hash
gate_actionA

Pre-execution gate; signs the decision and returns APPROVED, DENIED, or PENDING_APPROVAL.

Both outcomes hit the audit trail. After an APPROVED gate, call
complete_action(gate_id, result) to bind the outcome into a bilateral receipt.

Args:
    action_type: The action to gate (e.g. "data:delete:users", "tool:execute:sql")
    agent_id: The agent requesting the action
    tool_name: Optional name of the tool being invoked
    arguments: Optional JSON string of the tool arguments
    risk_context: Optional description of why this action is risky
complete_actionA

Sign the outcome of a gate-approved action and link it to the approval signature.

Produces a bilateral receipt: approval + outcome bound by gate_id. Required to close
the audit gap where approval is provable but result is not.

Args:
    gate_id: The gate_id returned by gate_action when it approved the action
    result: A description or JSON string of the action's outcome
enforced_tool_callA

Strong-enforcement path: policy-check + (optional) forward + sign request and response.

With tool_endpoint set, the approved call is forwarded and request+response are signed
together as one bilateral receipt. Without it, an approval token is returned and the
agent must call complete_action(call_id, result) to close the receipt.

Args:
    tool_name: Name of the tool to execute
    agent_id: The agent requesting the tool call
    arguments: Optional JSON string of tool arguments
    tool_endpoint: Optional HTTP endpoint to forward the approved call to
create_tool_policyA

Upsert a local tool enforcement policy used by gate_action and enforced_tool_call.

Policies are evaluated in-process (no API hop). Setting tool_endpoint lets
enforced_tool_call forward the call and sign request+response as a bilateral receipt.

Args:
    tool_name: Name of the tool to create a policy for
    risk_level: Risk classification - "low", "medium", or "high"
    require_approval: If true, high-risk tools need human approval before execution
    max_calls_per_minute: Rate limit (0 = unlimited)
    blocked: If true, the tool is completely blocked
    hidden: If true, the tool is invisible - not listed and treated as nonexistent
    tool_endpoint: Optional HTTP endpoint to forward approved calls to
list_tool_policiesA

List all active local tool enforcement policies.

delete_tool_policyB

Remove a local enforcement policy for a tool.

Args:
    tool_name: Name of the tool to remove the policy for
scan_tool_definitionA

Scan an MCP tool definition for security threats.

Checks for prompt injection, hidden unicode, dangerous schema fields,
typosquatting, and hardcoded secrets. Returns a risk assessment.

Args:
    tool_name: The tool name to scan
    description: The tool description to scan
    input_schema: Optional JSON string of the tool's input schema
scan_all_toolsA

Scan every registered tool policy for security threats.

Checks tool names for typosquatting and hidden unicode. Returns a summary with per-tool risk assessments.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jagmarques/asqav-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server