schedule_accounts_follow_ups
AI agents use schedule_accounts_follow_ups to create or update resources in Salesforce Basic MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Basic MCP Server environment.
The tool name strongly suggests scheduling follow-up activities (creating new task/calendar entries or modifying account activity plans), which is a reversible Write operation. The empty description prevents higher confidence, but the naming convention and context among read-only siblings indicate data creation rather than destructive action.
From the tool's definition Tool name 'schedule_accounts_follow_ups' indicates creation/modification of calendar or task records. Description is empty, limiting confidence.
Attacks that exploit this kind of access
schedule_accounts_follow_ups. It is categorised as a Write tool in the Salesforce Basic MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Salesforce Basic MCP Server MCP server in PolicyLayer and add a rule for schedule_accounts_follow_ups: 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 Salesforce Basic MCP Server. Nothing to install.
schedule_accounts_follow_ups 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 schedule_accounts_follow_ups 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 schedule_accounts_follow_ups. 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.
schedule_accounts_follow_ups is provided by the Salesforce Basic MCP Server MCP server (luis-e-dev/my-new-mcp-server). 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 →