AI agents use setup_profile to create or update resources in Crosswalk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crosswalk environment.
This tool writes user profile data to storage in a structured format, making it a Write operation. Severity is medium because misuse could result in incorrect profile information being stored, affecting job recommendations and application quality, but the impact is reversible through updates or re-entry. High confidence due to clear 'store' language in the description.
From the tool's definition 'Store a structured profile' indicates the tool creates or modifies persistent user data. The description does not mention deletion or destructive operations, nor does it execute arbitrary code or handle financial transactions.
Attacks that exploit this kind of access
Store a structured profile from a free-form description of the user. It is categorised as a Write tool in the Crosswalk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crosswalk MCP server in PolicyLayer and add a rule for setup_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 Crosswalk. Nothing to install.
setup_profile 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 setup_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 setup_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.
setup_profile is provided by the Crosswalk MCP server (mohakgarg5/crosswalk-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 →