List audit logs with optional filtering. Args: task_id: Filter by task ID operation: Filter by operation type (e.g., 'create_task', 'complete_task') client_name: Filter by client name since: Filter logs after this datetime (ISO format, e.g., '2025-12-11T09:00:00') until: Filter logs before this d...
AI agents call list_audit_logs to retrieve information from Taskdog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only retrieval of audit log records with filtering options. It has no side effects, does not create, modify, delete, or execute anything. The blast radius of misuse is minimal—an agent could retrieve audit logs but cannot alter task state or perform actions. Classified as Read with low severity.
From the tool's definition Tool description states it 'List audit logs with optional filtering' and returns 'logs list and metadata'. All parameters are filter/query options (task_id, operation, client_name, since, until, failed, limit).
Documented attack patterns abuse exactly the kind of access list_audit_logs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taskdog, and nothing reaches the server without passing your rules. This is the rule we recommend for list_audit_logs:
{
"version": "1",
"default": "deny",
"tools": {
"list_audit_logs": {}
}
}list_audit_logs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List audit logs with optional filtering. Args: task_id: Filter by task ID operation: Filter by operation type (e.g., 'create_task', 'complete_task') client_name: Filter by client name since: Filter logs after this datetime (ISO format, e.g., '2025-12-11T09:00:00') until: Filter logs before this datetime (ISO format, e.g., '2025-12-11T17:00:00') failed: If True, only show failed operations limit: Maximum number of logs to return Returns: Dictionary with logs list and metadata. It is categorised as a Read tool in the Taskdog MCP Server, which means it retrieves data without modifying state.
Register the Taskdog MCP server in PolicyLayer and add a rule for list_audit_logs: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Taskdog. Nothing to install.
list_audit_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_audit_logs rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_audit_logs. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_audit_logs is provided by the Taskdog MCP server (kohei-wada/taskdog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taskdog, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 Taskdog tools catalogued and risk-classified — across an index of 43,000+ MCP servers.