AI agents use add_code_source to create or update resources in Memex — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memex environment.
The tool performs a Write operation: it adds a new code source, which creates a new data entry in the system's memory or configuration. This is reversible (sources can be removed or updated later). The severity is medium because misconfigured or malicious code sources could be added, potentially affecting downstream operations, but the action itself is not destructive, financial, or immediately executable.
From the tool's definition The tool name 'add_code_source' suggests adding or registering a code source. In the context of a centralized agentic memory and MCP gateway, this would create or register a new code source entry in the system, constituting a reversible data modification.
Attacks that exploit this kind of access
add_code_source. It is categorised as a Write tool in the Memex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memex MCP server in PolicyLayer and add a rule for add_code_source: 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 Memex. Nothing to install.
add_code_source is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_code_source 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 add_code_source. 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.
add_code_source is provided by the Memex MCP server (queflyhq/memex). 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 →