Submit a pitch deck (PDF) to the caller's Caplia pipeline. The deck flows through the same intake pipeline as web uploads and email forwards: text extraction → company shell creation → CRI scoring → thesis matching. Returns { job_id, status: "queued", poll_url } immediately; use caplia_get_job wi...
Risk signalsAccepts file system path (filename)
Part of the Caplia server.
Free to start. No card required.
AI agents use caplia_submit_deck to create or modify resources in Caplia. 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 caplia_submit_deck 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 Caplia.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"caplia_submit_deck": {
"limits": [
{
"counter": "caplia_submit_deck_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Caplia policy for all 12 tools.
These attack patterns abuse exactly the kind of access caplia_submit_deck 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.
Submit a pitch deck (PDF) to the caller's Caplia pipeline. The deck flows through the same intake pipeline as web uploads and email forwards: text extraction → company shell creation → CRI scoring → thesis matching. Returns { job_id, status: "queued", poll_url } immediately; use caplia_get_job with the returned id to watch the company and scores land (typically 30s-2min). Requires a key with the write scope.. It is categorised as a Write tool in the Caplia MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Caplia MCP server in PolicyLayer and add a rule for caplia_submit_deck: 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 Caplia. Nothing to install.
caplia_submit_deck 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 caplia_submit_deck 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 caplia_submit_deck. 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.
caplia_submit_deck is provided by the Caplia MCP server (https://mcp.venture.caplia.ai/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Caplia 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.