Read all stored AI context entries — persistent key-value pairs (preferences, project facts, coding standards) that are injected into every AI session via context-sync.
AI agents call context_sync_read to retrieve information from Scan Your Ai Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves data (context entries, preferences, project facts, coding standards) without modifying, deleting, or executing anything. It is a pure read operation with no side effects. The severity is low because exposure of preference and project metadata presents minimal risk compared to tools that modify systems or execute arbitrary code.
From the tool's definition Tool name includes 'read'; description states 'Read all stored AI context entries' and describes retrieval of 'persistent key-value pairs' with no modification, deletion, or execution capabilities mentioned.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Read all stored AI context entries — persistent key-value pairs (preferences, project facts, coding standards) that are injected into every AI session via context-sync. It is categorised as a Read tool in the Scan Your Ai Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Scan Your Ai Toolkit MCP server in PolicyLayer and add a rule for context_sync_read: 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 Scan Your Ai Toolkit. Nothing to install.
context_sync_read 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 context_sync_read 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 context_sync_read. 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.
context_sync_read is provided by the Scan Your Ai Toolkit MCP server (sakthivelchan89/scan_your_ai_toolkit). 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 →