Kullanıcının kendi audit loglarını getirir
AI agents call get_my_audit_logs to retrieve information from MCP JSON Database Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical audit log data for the authenticated user. It is a read-only query operation that does not modify, delete, or execute any actions. The scope is limited to the user's own logs (not system-wide), further reducing risk. No data is altered, destroyed, or financial operations are triggered.
From the tool's definition Tool name 'get_my_audit_logs' and description 'Kullanıcının kendi audit loglarını getirir' (Turkish: 'Returns the user's own audit logs') indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Kullanıcının kendi audit loglarını getirir. It is categorised as a Read tool in the MCP JSON Database Server MCP Server, which means it retrieves data without modifying state.
Register the MCP JSON Database Server MCP server in PolicyLayer and add a rule for get_my_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 MCP JSON Database Server. Nothing to install.
get_my_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 get_my_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 get_my_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.
get_my_audit_logs is provided by the MCP JSON Database Server MCP server (yusuferenkt/mcp-database). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →