AI agents call scan_wrike to retrieve information from N0s1 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and scans existing data from Wrike (tasks and comments) to identify leaked secrets. It performs analysis on data but does not create, modify, delete, or execute operations. The scanning is for detection purposes only, making it a Read operation. Severity is low because the tool itself does not move money, execute code, or irreversibly alter data—it only accesses and analyzes existing information.
From the tool's definition Tool description explicitly states 'Read Wrike tasks and comments to detect leaked secrets'; the verb 'Read' and the detection purpose indicate data retrieval without modification or execution.
Attacks that exploit this kind of access
Read Wrike tasks and comments to detect leaked secrets (API keys, tokens, passwords). It is categorised as a Read tool in the N0s1 MCP Server, which means it retrieves data without modifying state.
Register the N0s1 MCP server in PolicyLayer and add a rule for scan_wrike: 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 N0s1. Nothing to install.
scan_wrike 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 scan_wrike 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 scan_wrike. 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.
scan_wrike is provided by the N0s1 MCP server (spark1security/n0s1-mcp). 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 →