Read the beta profile contract when the profile API is available.
AI agents call profile.get to retrieve information from Lore Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to retrieve a profile contract. The description clearly indicates it reads/fetches data from the profile API without modifying, deleting, or executing anything. No side effects are mentioned or implied. This is a straightforward data retrieval operation, making it a Read category tool with low severity.
From the tool's definition Tool name 'profile.get' and description 'Read the beta profile contract when the profile API is available' explicitly use the word 'Read' and indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Read the beta profile contract when the profile API is available. It is categorised as a Read tool in the Lore Context MCP Server, which means it retrieves data without modifying state.
Register the Lore Context MCP server in PolicyLayer and add a rule for profile.get: 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 Lore Context. Nothing to install.
profile.get 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 profile.get 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 profile.get. 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.
profile.get is provided by the Lore Context MCP server (Lore-Context/lore-context). 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 →