Generate a ready-to-share social-media post (tweet, Bluesky, Mastodon, LinkedIn, Telegram) about a result the user just received from another VC Deal Flow Signal tool, plus the install command for the MCP server. Returns the post body, character counts per platform, and one-click intent URLs to c...
Part of the GitDealFlow Signal server.
Free to start. No card required.
AI agents use share_result to create or modify resources in GitDealFlow Signal. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call share_result repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach GitDealFlow Signal.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"share_result": {
"limits": [
{
"counter": "share_result_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full GitDealFlow Signal policy for all 8 tools.
These attack patterns abuse exactly the kind of access share_result gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Generate a ready-to-share social-media post (tweet, Bluesky, Mastodon, LinkedIn, Telegram) about a result the user just received from another VC Deal Flow Signal tool, plus the install command for the MCP server. Returns the post body, character counts per platform, and one-click intent URLs to compose the post in each network. WHEN TO USE: - The user just got a get_trending_startups / search_startups_by_sector / get_startup_signal / get_deep_signal result and says 'share this', 'tweet this', 'post this', or 'how do I tell people about this?'. - The user is writing a thread/post about startup engineering signals and wants the canonical install command + share copy. DO NOT USE FOR: - Posting on the user's behalf — this tool only composes the text + intent URLs. The user must click and confirm in the destination network. - Generating fake or speculative results — pass real data the agent received from another tool call. BEHAVIOR: - Read-only, idempotent, no side effects, no authentication. - Composes platform-specific posts (Twitter ≤275 chars, Bluesky ≤295, Mastodon ≤495, LinkedIn ≤695, Telegram ≤995) with a consistent hook + insight + install URL. - Returns intent URLs (e.g. https://x.com/intent/post?text=...) so the user/agent can open the destination network with the post pre-filled. - Always includes the canonical install command npx @gitdealflow/mcp-signal and the SSRN paper link for credibility. PARAMETERS: - summary (string, required, 10-200 chars) — the one-line takeaway to share. - network (string, optional) — 'twitter' | 'bluesky' | 'mastodon' | 'linkedin' | 'telegram' | 'all' (default: 'all'). - mention_handle (boolean, optional, default false) — include @data_nerd attribution (twitter/bluesky/mastodon only).. It is categorised as a Write tool in the GitDealFlow Signal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitDealFlow Signal MCP server in PolicyLayer and add a rule for share_result: 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 GitDealFlow Signal. Nothing to install.
share_result 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 share_result 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 share_result. 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.
share_result is provided by the GitDealFlow Signal MCP server (kindrat86/mcp-deal-flow-signal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 GitDealFlow Signal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.