Add a certification.
AI agents use add_certification to create or update resources in LinkedIn Profile MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LinkedIn Profile MCP Server environment.
This tool creates or adds a new certification record to a LinkedIn profile, which is a reversible modification of professional data. While it modifies user credentials (which could affect professional reputation if misused by an agent), the action itself is not destructive, financial, or executable code.
From the tool's definition Tool name 'add_certification' and description 'Add a certification' indicate creating/adding a new credential to a LinkedIn profile. The verb 'add' combined with 'certification' clearly signals a write/create operation that modifies profile data.
Attacks that exploit this kind of access
Add a certification. It is categorised as a Write tool in the LinkedIn Profile MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LinkedIn Profile MCP Server MCP server in PolicyLayer and add a rule for add_certification: 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 LinkedIn Profile MCP Server. Nothing to install.
add_certification 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_certification 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_certification. 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_certification is provided by the LinkedIn Profile MCP Server MCP server (thejosem4/linkedin-profile-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 →