AI agents call get_teammate to retrieve information from Frontapp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves teammate information by ID without modifying, deleting, or executing any operations. It is a standard data retrieval function. The severity is low because exposing teammate details poses minimal risk compared to financial or destructive operations, though some organizational sensitivity may apply depending on data classification policies.
From the tool's definition Tool name 'get_teammate' and description 'Get details of a specific teammate by ID' indicate a retrieval operation. The verb 'Get' and the retrieval context confirm this is a read-only query with no side effects.
Documented attack patterns abuse exactly the kind of access get_teammate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Frontapp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_teammate:
{
"version": "1",
"default": "deny",
"tools": {
"get_teammate": {}
}
}get_teammate 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 details of a specific teammate by ID. It is categorised as a Read tool in the Frontapp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Frontapp MCP Server MCP server in PolicyLayer and add a rule for get_teammate: 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 Frontapp MCP Server. Nothing to install.
get_teammate 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_teammate 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_teammate. 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_teammate is provided by the Frontapp MCP Server MCP server (zqushair/frontapp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Frontapp MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
151 Frontapp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.