Cyphrex

get_audit_log

Get Cyphrex audit log for an agent

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`agentId`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedAug 17, 2026

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

removedInput schema / properties / apiKey

Removed value: -{
-  "minLength": 1,
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "agentId",
-  "apiKey"
-]New value: +[
+  "agentId"
+]

First observedApr 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the action ('Get') without revealing any behavioral traits such as pagination, ordering, permission requirements, or return format. The presence of a 'limit' parameter hints at pagination, but the description does not mention it.

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?

The description is a single, clear sentence with no superfluous words. It is front-loaded and efficiently communicates the core purpose. Perfect conciseness for a simple tool.

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

Completeness2/5

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

While the tool is conceptually simple, the description lacks important context: no output schema is provided, and the description does not explain the return structure, the meaning of 'limit', or any default behaviors. The agent would need to infer too much about the audit log contents and parameter effects.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the description adds no parameter details. The required 'agentId' is loosely implied by 'for an agent', but the optional 'limit' parameter is completely unexplained. The description provides minimal value beyond what the schema already shows.

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?

The description uses a specific verb ('Get') and resource ('Cyphrex audit log'), scoped to 'an agent'. This clearly distinguishes it from sibling tools like 'log_action' (which writes) or 'check_action' (which verifies). No ambiguity.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description neither states typical use cases nor excluded scenarios. With sibling tools like 'log_action' and 'check_action', some differentiation or usage context would be helpful, but it is entirely absent.

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

All Cyphrex tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation5/5

Each tool targets a distinct action: checking proposed actions, logging/reading audit data, proxying requests, registering/verifying agents, scanning different payload types, and setting profiles. The separation between check_action and scan_mcp_tool_result is clear from their descriptions (proposed action vs. upstream result).

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., check_action, get_audit_log, set_behavior_profile). No mixing of styles or vague verbs beyond standard operation names.

Tool Count5/5

With 9 tools, the set is well-scoped for a security-focused MCP governance server. Each tool addresses a clear need without redundancy or excessive granularity.

Completeness4/5

The tool set covers the core lifecycle: agent registration, verification, behavior profiling, action checking/logging, audit retrieval, proxying, and scanning. Minor gaps include no explicit agent removal or policy management tools, but these may be intentionally outside the server's scope.

Resources

Need Help?