Get patterns and conventions learned from this codebase\
AI agents call get_developer_profile to retrieve information from In Memoria without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves learned patterns and conventions from memory—a read-only query operation. It returns information about developer practices without creating, modifying, deleting, or executing anything. No data is altered, no code is executed, and no external operations are triggered.
From the tool's definition Tool name 'get_developer_profile' and description 'Get patterns and conventions learned from this codebase' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_developer_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and In Memoria, and nothing reaches the server without passing your rules. This is the rule we recommend for get_developer_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_developer_profile": {}
}
}get_developer_profile 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.
Get patterns and conventions learned from this codebase\. It is categorised as a Read tool in the In Memoria MCP Server, which means it retrieves data without modifying state.
Register the In Memoria MCP server in PolicyLayer and add a rule for get_developer_profile: 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 In Memoria. Nothing to install.
get_developer_profile 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_developer_profile 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_developer_profile. 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_developer_profile is provided by the In Memoria MCP server (pi22by7/in-memoria). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 In Memoria tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 In Memoria tools catalogued and risk-classified — across an index of 42,500+ MCP servers.