AI agents call get_teammates 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 information about teammates from Frontapp's system. It is a read-only operation that has no side effects—it does not create, modify, delete, or trigger any external operations. The blast radius of misuse is minimal, as an AI agent gaining access to teammate listings poses low risk compared to tools that could modify communications, delete data, or execute arbitrary operations.
From the tool's definition Tool name 'get_teammates' and description 'Get a list of teammates from Frontapp' indicate a retrieval operation that queries team member data without modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access get_teammates 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_teammates:
{
"version": "1",
"default": "deny",
"tools": {
"get_teammates": {}
}
} get_teammates 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 a list of teammates from Frontapp. 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_teammates: 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_teammates 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_teammates 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_teammates. 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_teammates 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.